This is an automated email from the ASF dual-hosted git repository.
dzamo pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/drill-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new d35f689 Fix blog post typos.
d35f689 is described below
commit d35f689d7637cb80b647fd5a808c21859d936c50
Author: James Turton <[email protected]>
AuthorDate: Fri Jul 9 16:18:45 2021 +0200
Fix blog post typos.
---
blog/2021/07/09/streaming-data-from-the-rest-api/index.html | 4 ++--
zh/blog/2021/07/09/streaming-data-from-the-rest-api/index.html | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/blog/2021/07/09/streaming-data-from-the-rest-api/index.html
b/blog/2021/07/09/streaming-data-from-the-rest-api/index.html
index 04e3dcb..a6ffe63 100644
--- a/blog/2021/07/09/streaming-data-from-the-rest-api/index.html
+++ b/blog/2021/07/09/streaming-data-from-the-rest-api/index.html
@@ -153,9 +153,9 @@
<div class="addthis_sharing_toolbox"></div>
<article class="post-content">
- <p>Anyone who’s used a UNIX pipe, or even just watched something on
Netflix, is at least a little familiar with the idea of processing data in a
streaming fashion. While your data are in small volume compared to available
memory and I/O speeds, streaming is something you can afford to dispense with.
But when you cannot fit an entire dataset in RAM, or when if you have to
download an entire 4K movie before you can start playing it, then streaming
data processing can make a game chan [...]
+ <p>Anyone who’s used a UNIX pipe, or even just watched something on
Netflix, is at least a little familiar with the idea of processing data in a
streaming fashion. While your data are small in size compared to available
memory and I/O speeds, streaming is something you can afford to dispense with.
But when you cannot fit an entire dataset in RAM, or when you have to download
an entire 4K movie before you can start playing it, then streaming data
processing can make a game changing [...]
-<p>With the relase of version 1.19, Drill will stream JSON query result data
over an HTTP response to the client that initiated the query using the REST
API. And if anything can easily get big compared to your available RAM or
network speed, it’s query results coming back from Drill. It’s important to
note here that JSON over HTTP is never going to be the most <em>efficient</em>
way to move big data around<sup id="fnref:1" role="doc-noteref"><a href="#fn:1"
class="footnote">1</a></sup> [...]
+<p>With the release of version 1.19, Drill will stream JSON query result data
over an HTTP response to the client that initiated the query using the REST
API. And if anything can easily get big compared to your available RAM or
network speed, it’s query results coming back from Drill. It’s important to
note here that JSON over HTTP is never going to be the most <em>efficient</em>
way to move big data around<sup id="fnref:1" role="doc-noteref"><a href="#fn:1"
class="footnote">1</a></sup [...]
<p>Where JSON and HTTP <em>do</em> win is universality: today it’s hard to
imagine a client hardware and software stack that doesn’t provide JSON and HTTP
out of the box with minimal effort. So it’s important that they work as well
as is possible, in spite of the alternatives that exist. The new streaming
query results delivery on the server side means that Drill’s heap memory isn’t
pressurised by having to buffer entire result sets before it starts to transmit
them over the network. [...]
diff --git a/zh/blog/2021/07/09/streaming-data-from-the-rest-api/index.html
b/zh/blog/2021/07/09/streaming-data-from-the-rest-api/index.html
index 209378d..c97d89f 100644
--- a/zh/blog/2021/07/09/streaming-data-from-the-rest-api/index.html
+++ b/zh/blog/2021/07/09/streaming-data-from-the-rest-api/index.html
@@ -153,9 +153,9 @@
<div class="addthis_sharing_toolbox"></div>
<article class="post-content">
- <p>Anyone who’s used a UNIX pipe, or even just watched something on
Netflix, is at least a little familiar with the idea of processing data in a
streaming fashion. While your data are in small volume compared to available
memory and I/O speeds, streaming is something you can afford to dispense with.
But when you cannot fit an entire dataset in RAM, or when if you have to
download an entire 4K movie before you can start playing it, then streaming
data processing can make a game chan [...]
+ <p>Anyone who’s used a UNIX pipe, or even just watched something on
Netflix, is at least a little familiar with the idea of processing data in a
streaming fashion. While your data are small in size compared to available
memory and I/O speeds, streaming is something you can afford to dispense with.
But when you cannot fit an entire dataset in RAM, or when you have to download
an entire 4K movie before you can start playing it, then streaming data
processing can make a game changing [...]
-<p>With the relase of version 1.19, Drill will stream JSON query result data
over an HTTP response to the client that initiated the query using the REST
API. And if anything can easily get big compared to your available RAM or
network speed, it’s query results coming back from Drill. It’s important to
note here that JSON over HTTP is never going to be the most <em>efficient</em>
way to move big data around<sup id="fnref:1" role="doc-noteref"><a href="#fn:1"
class="footnote">1</a></sup> [...]
+<p>With the release of version 1.19, Drill will stream JSON query result data
over an HTTP response to the client that initiated the query using the REST
API. And if anything can easily get big compared to your available RAM or
network speed, it’s query results coming back from Drill. It’s important to
note here that JSON over HTTP is never going to be the most <em>efficient</em>
way to move big data around<sup id="fnref:1" role="doc-noteref"><a href="#fn:1"
class="footnote">1</a></sup [...]
<p>Where JSON and HTTP <em>do</em> win is universality: today it’s hard to
imagine a client hardware and software stack that doesn’t provide JSON and HTTP
out of the box with minimal effort. So it’s important that they work as well
as is possible, in spite of the alternatives that exist. The new streaming
query results delivery on the server side means that Drill’s heap memory isn’t
pressurised by having to buffer entire result sets before it starts to transmit
them over the network. [...]
