[
https://issues.apache.org/jira/browse/DRILL-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13909800#comment-13909800
]
Jason Altekruse commented on DRILL-381:
---------------------------------------
I was hoping to get some feedback first. I was a bit torn about the format for
the various value types over the wire. I knew that we wold want to read these
values in from some sort of config file for the initial value populations when
we actually make a release, right now they are just hard coded. For this reason
I just re-used the string representations that would be used for the config
files for sending the values throughout the cluster (I used the standard
toString and parsing methods for the numeric types, and a UTF-8 encoding for
strings). It does mean that every time a value is received we have to call a
parsing method. I wasn't sure we would ever define enough options for this to
be an issue, or if there would even be any significant performance enhancement
over re-interpreting a raw byte stream as the appropriate java values, rather
than parsing ascii.
> Implement SQL Options Statements
> --------------------------------
>
> Key: DRILL-381
> URL: https://issues.apache.org/jira/browse/DRILL-381
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Jason Altekruse
> Attachments: 0001-start-of-storage-system-for-drill-options.patch
>
>
> We need to implement a system for passing and storing options at the global
> and session level. Some example options include, explain plan format,
> allowing quoted identifiers, null handling (concat null yields null). This
> involves creating a notion of a user session, as previously nothing was
> stored per user session.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
