Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Mon, 24 Jul 2017 15:42:00 +0000 (UTC)
From: "Abhishek Girish (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.13089564.1500910861000.316432.1500910920053@Atlassian.JIRA>
In-Reply-To: <JIRA.13089564.1500910861000@Atlassian.JIRA>
References: <JIRA.13089564.1500910861000@Atlassian.JIRA> <JIRA.13089564.1500910861986@jira-lw-us.apache.org>
Subject: [jira] [Created] (DRILL-5684) Add documentation for lineDelimiter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 24 Jul 2017 15:42:05 -0000

Abhishek Girish created DRILL-5684:
--------------------------------------

             Summary: Add documentation for lineDelimiter
                 Key: DRILL-5684
                 URL: https://issues.apache.org/jira/browse/DRILL-5684
             Project: Apache Drill
          Issue Type: Task
          Components: Documentation
    Affects Versions: 1.10.0, 1.11.0
            Reporter: Abhishek Girish
            Assignee: Bridget Bevens


We need to document the lineDelimiter attribute in [1], [2]. Also possibly a note that if using Drill on Windows, the new line delimiter in text files can be different from that on Linux / Mac. If the delimited text data has \r\n as the lineDelimiter (carriage return & new line) and querying it from Drill doesn't work as expected, we need to update the format plugin, as shown in the example below:
{code}
"csv": {
      "type": "text",
      "extensions": [
        "csv"
      ],
      "lineDelimiter": "\r\n",
      "extractHeader": true,
      "delimiter": ","
    }
{code}

[1] https://drill.apache.org/docs/plugin-configuration-basics/#list-of-attributes-and-definitions
[2] https://drill.apache.org/docs/text-files-csv-tsv-psv/#configuring-drill-to-read-text-files


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)