[jira] [Commented] (DRILL-8243) Move JSON Config Options Out of HTTP Plugin
[ https://issues.apache.org/jira/browse/DRILL-8243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17546849#comment-17546849 ] ASF GitHub Bot commented on DRILL-8243: --- cgivre opened a new pull request, #2570: URL: https://github.com/apache/drill/pull/2570 # [DRILL-8243](https://issues.apache.org/jira/browse/DRILL-): Move JSON Config Options Out of HTTP Plugin ## Description As part of [DRILL-8241](https://issues.apache.org/jira/browse/DRILL-8241), this PR moves the json configuration options out of the HTTP plugin and creates a file which can be used for other plugins that consume JSON data. The idea being that all such plugins, like Druid, ES, Mongo, can set the same JSON options for each plugin instance w/o having to duplicate config code. ## Documentation No user facing changes. ## Testing Ran existing unit tests and tested manually. > Move JSON Config Options Out of HTTP Plugin > --- > > Key: DRILL-8243 > URL: https://issues.apache.org/jira/browse/DRILL-8243 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - JSON >Affects Versions: 1.20.1 >Reporter: Charles Givre >Assignee: Charles Givre >Priority: Minor > Fix For: 2.0.0 > > > As part of DRILL-8241, this PR moves the json configuration options out of > the HTTP plugin and creates a file which can be used for other plugins that > consume JSON data. > The idea being that all such plugins, like Druid, ES, Mongo, can set the same > JSON options for each plugin instance w/o having to duplicate config code. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (DRILL-8241) Remove Deprecated JSON Reader
[ https://issues.apache.org/jira/browse/DRILL-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Givre updated DRILL-8241: - Description: This is a master ticket to remove the deprecated v1 JSON reader from Drill. This JSON reader is used in several places and removing it will ensure consistent behavior across all data sources. The V2, EVF based JSON reader has several advantages, including the possibility of schema provisioning, limit pushdowns and others. Here are the tasks which need to be completed to fully remove the v1 JSON reader. * Complete DRILL-5955 which adds support for the UNION vector to the EVF Json reader. * Convert the convert_fromJSON functions to V2 (DRILL-8239) * Convert the Druid Storage Plugin to V2 * Convert MongoDB Storage Plugin to V2. (Note the MongoDB plugin uses an EVF-based BSON reader as well as the V1 JSON reader) * Remove all V1-based unit tests * Migrate the JsonOptions from the HTTP Storage Plugin to global location to allow other plugins and users of JSON to set JSON configuration at a more granular level. (DRILL-8243) * Remove extraneous configuration options. * Bug fix HTTP UDFs (DRILL-8242) was: This is a master ticket to remove the deprecated v1 JSON reader from Drill. This JSON reader is used in several places and removing it will ensure consistent behavior across all data sources. The V2, EVF based JSON reader has several advantages, including the possibility of schema provisioning, limit pushdowns and others. Here are the tasks which need to be completed to fully remove the v1 JSON reader. * Complete DRILL-5955 which adds support for the UNION vector to the EVF Json reader. * Convert the convert_fromJSON functions to V2 (DRILL-8239) * Convert the Druid Storage Plugin to V2 * Convert MongoDB Storage Plugin to V2. (Note the MongoDB plugin uses an EVF-based BSON reader as well as the V1 JSON reader) * Remove all V1-based unit tests * Migrate the JsonOptions from the HTTP Storage Plugin to global location to allow other plugins and users of JSON to set JSON configuration at a more granular level. * Remove extraneous configuration options. * Bug fix HTTP UDFs (DRILL-8242) > Remove Deprecated JSON Reader > - > > Key: DRILL-8241 > URL: https://issues.apache.org/jira/browse/DRILL-8241 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - JSON >Affects Versions: 1.20.1 >Reporter: Charles Givre >Priority: Major > Fix For: 2.0.0 > > > This is a master ticket to remove the deprecated v1 JSON reader from Drill. > This JSON reader is used in several places and removing it will ensure > consistent behavior across all data sources. > The V2, EVF based JSON reader has several advantages, including the > possibility of schema provisioning, limit pushdowns and others. > Here are the tasks which need to be completed to fully remove the v1 JSON > reader. > * Complete DRILL-5955 which adds support for the UNION vector to the EVF > Json reader. > * Convert the convert_fromJSON functions to V2 (DRILL-8239) > * Convert the Druid Storage Plugin to V2 > * Convert MongoDB Storage Plugin to V2. (Note the MongoDB plugin uses an > EVF-based BSON reader as well as the V1 JSON reader) > * Remove all V1-based unit tests > * Migrate the JsonOptions from the HTTP Storage Plugin to global location to > allow other plugins and users of JSON to set JSON configuration at a more > granular level. (DRILL-8243) > * Remove extraneous configuration options. > * Bug fix HTTP UDFs (DRILL-8242) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (DRILL-8243) Move JSON Config Options Out of HTTP Plugin
Charles Givre created DRILL-8243: Summary: Move JSON Config Options Out of HTTP Plugin Key: DRILL-8243 URL: https://issues.apache.org/jira/browse/DRILL-8243 Project: Apache Drill Issue Type: Improvement Components: Storage - JSON Affects Versions: 1.20.1 Reporter: Charles Givre Assignee: Charles Givre Fix For: 2.0.0 As part of DRILL-8241, this PR moves the json configuration options out of the HTTP plugin and creates a file which can be used for other plugins that consume JSON data. The idea being that all such plugins, like Druid, ES, Mongo, can set the same JSON options for each plugin instance w/o having to duplicate config code. -- This message was sent by Atlassian Jira (v8.20.7#820007)
