You'll use it again later in this article when you get some JSON from a remote source.
在本文的后面，当从一个远程源获取JSON时，您将再次使用它。
Later, you'll learn how to add more projects from local and remote source-code repositories.
稍后您将会学习到如何添加来自本地和远程源代码仓库的更多项目。
Assume that there is a LINEITEM fact table on one remote source and a PART dimension table on another.
假设在一个远程数据源上有一个lineitem事实表，在另一个远程数据源上有一个part维表。
F2PC to the remote source is enabled, and the federated server's logs are on a disk with write caching (yellow).
远程数据源启用了F2PC，且联邦服务器的日志放在带写缓存的磁盘上(黄色)。
F2PC to the remote source is enabled, and the federated server's logs are on a disk without write caching (green).
远程数据源启用了F2PC，且联邦服务器的日志放在无写缓存的磁盘上(绿色)。
In this example, assume that each "shipped" query requires complex, time consuming computation at the remote source.
在这个例子中，假设每个被“转发”的查询在远程数据源上都需要进行复杂的、比较耗时的计算。
Since only a single remote source is involved, enabling F2PC is not necessary — there are no multi-site transactions.
由于只涉及单个远程数据源，启用F2PC并无必要——这里不存在多站点事务。
Depending on the operation, allowing it to be evaluated on a remote source might help the overall performance of the query.
取决于操作的不同，允许在远程数据源上执行操作可能有助于查询的整体性能。
Even if such queries are pushed down to the remote source, they can be very costly, especially if the remote object is large.
那些查询即使被下推到远程数据源，其成本也非常高，当远程对象较大时，这一点尤其明显。
For relational sources, nickname statistics are usually automatically retrieved by lookup from the catalog of the remote source.
对于关系数据源，通常是通过自动查找远程数据源的编目来检索昵称统计信息的。
This means that even if multiple remote sources participate in a query, only one remote source or the federated server is active at any given moment.
这意味着，即使一个查询中涉及到多个远程数据源，在任何时候只有一个远程数据源或联邦服务器是活动的。
For example, a view based on a very complex query that returns only five rows (for example, a GROUP BY query) is costly to evaluate at the remote source.
例如，基于一个非常复杂的、只返回5行的查询(例如一个GROUPBY查询)的视图在远程数据源上计算起来代价较高。
The same user/password combination can also be used for the source, allowing you to copy from a remote source to a local directory: $ rsync --recursive user@remote:dira dirb.
还可以对源目录使用相同的用户/密码组合，从而从远程源目录复制到本地目录：$rsync --recursive user@remote:diradirb。
The difference is that by the time the rows from the blue SHIP have been received, the result set of the pink SHIP is hopefully ready and waiting to be retrieved from the remote source.
不同之处在于，当蓝色SHIP返回的行接收完毕之后，粉色SHIP返回的结果集很可能也已经准备就绪，可以马上从远程数据源获取。
The response time is influenced by the volume of data that need to be moved from remote source to federated server per transaction: the higher the data volume, the slower the response time.
响应时间受到每个事务需要从远程源传输到联合服务器的数据量的影响：数据量越大，响应时间越长。
Many server applications, such as Web servers, database servers, file servers, or mail servers, are oriented around processing a large number of short tasks that arrive from some remote source.
诸如web服务器、数据库服务器、文件服务器或邮件服务器之类的许多服务器应用程序都面向处理来自某些远程来源的大量短小的任务。
As a consequence, only the simplest SQL functionality is pushed down to the remote source, while more complex operations (grouping, joins, and so on) are virtually all done at the federated server.
因此，只有最简单的SQL功能被下推到远程数据源，而一些更复杂的操作(分组、连接等)实际上都是在联邦服务器上完成的。
Thus, Federation Server can push down only a few SQL operations through the standard ODBC wrapper to the remote source and executes most predicate evaluations, aggregations, sorts and joins locally.
因此，在使用标准的ODBC包装器的情况下，FederationServer只能将少数SQL操作下推到远程数据源，大多数谓词的计算、聚合、排序和连接仍然是在本地完成。
Local source data is first sampled at an original sampling rate and then resampled at a first resampling rate which is equal to the framing rate for transmitting said data to the remote source.
本地源数据首先以一个原始采样速率采样，然后以等于将所述数据发送到该远端源的帧速率的第一重复取样速率重复取样。
Local source data is first sampled at an original sampling rate and then resampled at a first resampling rate which is equal to the framing rate for transmitting said data to the remote source.
本地源数据首先以一个原始采样速率采样，然后以等于将所述数据发送到该远端源的帧速率的第一重复取样速率重复取样。
应用推荐