This is an automated email from the ASF dual-hosted git repository.
jackie pushed a commit to branch fix_doc_for_delimiter
in repository https://gitbox.apache.org/repos/asf/incubator-pinot.git
The following commit(s) were added to refs/heads/fix_doc_for_delimiter by this
push:
new 9448527 Address comment: add AVRO into standard format example
9448527 is described below
commit 9448527848e575a4d95203c68b020a1e4bb6f506
Author: Jackie (Xiaotian) Jiang <[email protected]>
AuthorDate: Mon Apr 8 13:51:52 2019 -0700
Address comment: add AVRO into standard format example
---
docs/pinot_hadoop.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/pinot_hadoop.rst b/docs/pinot_hadoop.rst
index 880b805..81f0728 100644
--- a/docs/pinot_hadoop.rst
+++ b/docs/pinot_hadoop.rst
@@ -90,11 +90,11 @@ You can then use the SegmentTarPush job to push segments
via the controller REST
Creating Pinot segments outside of Hadoop
-----------------------------------------
-Here is how you can create Pinot segments from standard formats like CSV/JSON.
+Here is how you can create Pinot segments from standard formats like
CSV/JSON/AVRO.
#. Follow the steps described in the section on :ref:`compiling-code-section`
to build pinot. Locate ``pinot-admin.sh`` in
``pinot-tools/target/pinot-tools=pkg/bin/pinot-admin.sh``.
-#. Create a top level directory containing all the CSV/JSON files that need to
be converted into segments.
-#. The file name extensions are expected to be the same as the format name
(*i.e* ``.csv``, or ``.json``), and are case insensitive. Note that the
converter expects the ``.csv`` extension even if the data is delimited using
tabs or spaces instead.
+#. Create a top level directory containing all the CSV/JSON/AVRO files that
need to be converted into segments.
+#. The file name extensions are expected to be the same as the format name
(*i.e* ``.csv``, ``.json`` or ``.avro``), and are case insensitive. Note that
the converter expects the ``.csv`` extension even if the data is delimited
using tabs or spaces instead.
#. Prepare a schema file describing the schema of the input data. The schema
needs to be in JSON format. See example later in this section.
#. Specifically for CSV format, an optional csv config file can be provided
(also in JSON format). This is used to configure parameters like the
delimiter/header for the CSV file etc. A detailed description of this follows
below.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
