[jira] [Resolved] (DRILL-7837) IntelliJ IDEA and Eclipse formatter file download should be unified
[ https://issues.apache.org/jira/browse/DRILL-7837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong resolved DRILL-7837. Reviewer: Charles Givre Resolution: Resolved > IntelliJ IDEA and Eclipse formatter file download should be unified > --- > > Key: DRILL-7837 > URL: https://issues.apache.org/jira/browse/DRILL-7837 > Project: Apache Drill > Issue Type: Improvement >Reporter: luocong >Assignee: luocong >Priority: Major > Fix For: 1.19.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (DRILL-7839) Update the doc and remove the formatter file on gh-pages branch
[ https://issues.apache.org/jira/browse/DRILL-7839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong resolved DRILL-7839. Reviewer: Charles Givre Resolution: Resolved > Update the doc and remove the formatter file on gh-pages branch > --- > > Key: DRILL-7839 > URL: https://issues.apache.org/jira/browse/DRILL-7839 > Project: Apache Drill > Issue Type: Sub-task >Reporter: luocong >Assignee: luocong >Priority: Major > Fix For: 1.19.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (DRILL-7838) Upload the IDEA and Eclipse formatter file to dev branch
[ https://issues.apache.org/jira/browse/DRILL-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong resolved DRILL-7838. Reviewer: Charles Givre Resolution: Resolved > Upload the IDEA and Eclipse formatter file to dev branch > > > Key: DRILL-7838 > URL: https://issues.apache.org/jira/browse/DRILL-7838 > Project: Apache Drill > Issue Type: Sub-task >Reporter: luocong >Assignee: luocong >Priority: Major > Fix For: 1.19.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DRILL-7839) Update the doc and remove the formatter file on gh-pages branch
luocong created DRILL-7839: -- Summary: Update the doc and remove the formatter file on gh-pages branch Key: DRILL-7839 URL: https://issues.apache.org/jira/browse/DRILL-7839 Project: Apache Drill Issue Type: Sub-task Reporter: luocong Assignee: luocong Fix For: 1.19.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DRILL-7838) Upload the IDEA and Eclipse formatter file to dev branch
luocong created DRILL-7838: -- Summary: Upload the IDEA and Eclipse formatter file to dev branch Key: DRILL-7838 URL: https://issues.apache.org/jira/browse/DRILL-7838 Project: Apache Drill Issue Type: Sub-task Reporter: luocong Assignee: luocong Fix For: 1.19.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DRILL-7837) IntelliJ IDEA and Eclipse formatter file download should be unified
luocong created DRILL-7837: -- Summary: IntelliJ IDEA and Eclipse formatter file download should be unified Key: DRILL-7837 URL: https://issues.apache.org/jira/browse/DRILL-7837 Project: Apache Drill Issue Type: Improvement Reporter: luocong Assignee: luocong Fix For: 1.19.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (DRILL-7552) Add Helpful Error Message on Storage Plugin Creation/Update
[
https://issues.apache.org/jira/browse/DRILL-7552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
luocong resolved DRILL-7552.
Reviewer: Charles Givre
Resolution: Resolved
> Add Helpful Error Message on Storage Plugin Creation/Update
> ---
>
> Key: DRILL-7552
> URL: https://issues.apache.org/jira/browse/DRILL-7552
> Project: Apache Drill
> Issue Type: Sub-task
> Components: Storage - Other
>Affects Versions: 1.17.0
>Reporter: Charles Givre
>Assignee: luocong
>Priority: Major
> Labels: error_message_improvement
> Fix For: 1.19.0
>
> Attachments: image-2020-01-26-16-47-46-398.png
>
>
> If you are attempting to create or update a storage plugin and for whatever
> reason an error occurs, the only error message that is displayed in the GUI
> is
> {code:java}
> Please retry: Error (unable to parse JSON)
> {code}
> This is unhelpful to the user as the user may have entered in valid JSON, but
> specified an invalid option. The error gives no indication as to what
> actually went wrong and how to fix.
> See example below:
> !image-2020-01-26-16-47-46-398.png!
> In this example, the cause of the error is the final option isMysql: false,
> which does not exist as a configuration option for the JDBC plugin.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (DRILL-7533) Convert Pcapng to EVF
[ https://issues.apache.org/jira/browse/DRILL-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong resolved DRILL-7533. Reviewer: Charles Givre Resolution: Resolved > Convert Pcapng to EVF > - > > Key: DRILL-7533 > URL: https://issues.apache.org/jira/browse/DRILL-7533 > Project: Apache Drill > Issue Type: Sub-task >Reporter: Arina Ielchiieva >Assignee: luocong >Priority: Major > Fix For: 1.19.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DRILL-7828) Refactor Pcap and Pcapng format plugin
luocong created DRILL-7828: -- Summary: Refactor Pcap and Pcapng format plugin Key: DRILL-7828 URL: https://issues.apache.org/jira/browse/DRILL-7828 Project: Apache Drill Issue Type: Sub-task Reporter: luocong Assignee: luocong Fix For: 1.19.0 We can check the file's magic number, If that magic number indicates PCAP then use the existing reader, If the magic number indicates PCAPNG, use the refactored NG reader. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DRILL-7827) Move the Pcap format plugin to contrib folder
[ https://issues.apache.org/jira/browse/DRILL-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong updated DRILL-7827: --- Parent: DRILL-7826 Issue Type: Sub-task (was: Improvement) > Move the Pcap format plugin to contrib folder > - > > Key: DRILL-7827 > URL: https://issues.apache.org/jira/browse/DRILL-7827 > Project: Apache Drill > Issue Type: Sub-task >Reporter: luocong >Assignee: luocong >Priority: Major > Fix For: 1.19.0 > > > If [DRILL-7533|https://issues.apache.org/jira/browse/DRILL-7533] is done, > then Pcapng format plugin move to contrib folder. Pcap format can do it too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DRILL-7827) Move the Pcap format plugin to contrib folder
luocong created DRILL-7827: -- Summary: Move the Pcap format plugin to contrib folder Key: DRILL-7827 URL: https://issues.apache.org/jira/browse/DRILL-7827 Project: Apache Drill Issue Type: Improvement Reporter: luocong Assignee: luocong Fix For: 1.19.0 If [DRILL-7533|https://issues.apache.org/jira/browse/DRILL-7533] is done, then Pcapng format plugin move to contrib folder. Pcap format can do it too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DRILL-7826) Merge Pcap and Pcapng format plugin based on EVF
luocong created DRILL-7826: -- Summary: Merge Pcap and Pcapng format plugin based on EVF Key: DRILL-7826 URL: https://issues.apache.org/jira/browse/DRILL-7826 Project: Apache Drill Issue Type: Improvement Reporter: luocong Assignee: luocong Fix For: 1.19.0 This is umbrella Jira to track down process of merging Pcap and Pcapng format plugin based on EVF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DRILL-7536) Convert Image format to EVF
[ https://issues.apache.org/jira/browse/DRILL-7536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong updated DRILL-7536: --- Fix Version/s: 1.19.0 > Convert Image format to EVF > --- > > Key: DRILL-7536 > URL: https://issues.apache.org/jira/browse/DRILL-7536 > Project: Apache Drill > Issue Type: Sub-task >Reporter: Arina Ielchiieva >Assignee: luocong >Priority: Major > Fix For: 1.19.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DRILL-7533) Convert Pcapng to EVF
[ https://issues.apache.org/jira/browse/DRILL-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong updated DRILL-7533: --- Fix Version/s: 1.19.0 > Convert Pcapng to EVF > - > > Key: DRILL-7533 > URL: https://issues.apache.org/jira/browse/DRILL-7533 > Project: Apache Drill > Issue Type: Sub-task >Reporter: Arina Ielchiieva >Assignee: luocong >Priority: Major > Fix For: 1.19.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (DRILL-7536) Convert Image format to EVF
[ https://issues.apache.org/jira/browse/DRILL-7536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong reassigned DRILL-7536: -- Assignee: luocong > Convert Image format to EVF > --- > > Key: DRILL-7536 > URL: https://issues.apache.org/jira/browse/DRILL-7536 > Project: Apache Drill > Issue Type: Sub-task >Reporter: Arina Ielchiieva >Assignee: luocong >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (DRILL-7533) Convert Pcapng to EVF
[ https://issues.apache.org/jira/browse/DRILL-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong reassigned DRILL-7533: -- Assignee: luocong (was: Charles Givre) > Convert Pcapng to EVF > - > > Key: DRILL-7533 > URL: https://issues.apache.org/jira/browse/DRILL-7533 > Project: Apache Drill > Issue Type: Sub-task >Reporter: Arina Ielchiieva >Assignee: luocong >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (DRILL-7525) Convert SequenceFiles to EVF
[ https://issues.apache.org/jira/browse/DRILL-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong resolved DRILL-7525. Reviewer: Charles Givre Resolution: Resolved > Convert SequenceFiles to EVF > > > Key: DRILL-7525 > URL: https://issues.apache.org/jira/browse/DRILL-7525 > Project: Apache Drill > Issue Type: Sub-task >Affects Versions: 1.17.0 >Reporter: Arina Ielchiieva >Assignee: luocong >Priority: Major > Fix For: 1.19.0 > > > Convert SequenceFiles to EVF -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DRILL-7552) Add Helpful Error Message on Storage Plugin Creation/Update
[
https://issues.apache.org/jira/browse/DRILL-7552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
luocong updated DRILL-7552:
---
Fix Version/s: 1.19.0
> Add Helpful Error Message on Storage Plugin Creation/Update
> ---
>
> Key: DRILL-7552
> URL: https://issues.apache.org/jira/browse/DRILL-7552
> Project: Apache Drill
> Issue Type: Sub-task
> Components: Storage - Other
>Affects Versions: 1.17.0
>Reporter: Charles Givre
>Assignee: luocong
>Priority: Major
> Labels: error_message_improvement
> Fix For: 1.19.0
>
> Attachments: image-2020-01-26-16-47-46-398.png
>
>
> If you are attempting to create or update a storage plugin and for whatever
> reason an error occurs, the only error message that is displayed in the GUI
> is
> {code:java}
> Please retry: Error (unable to parse JSON)
> {code}
> This is unhelpful to the user as the user may have entered in valid JSON, but
> specified an invalid option. The error gives no indication as to what
> actually went wrong and how to fix.
> See example below:
> !image-2020-01-26-16-47-46-398.png!
> In this example, the cause of the error is the final option isMysql: false,
> which does not exist as a configuration option for the JDBC plugin.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (DRILL-7552) Add Helpful Error Message on Storage Plugin Creation/Update
[
https://issues.apache.org/jira/browse/DRILL-7552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
luocong reassigned DRILL-7552:
--
Assignee: luocong
> Add Helpful Error Message on Storage Plugin Creation/Update
> ---
>
> Key: DRILL-7552
> URL: https://issues.apache.org/jira/browse/DRILL-7552
> Project: Apache Drill
> Issue Type: Sub-task
> Components: Storage - Other
>Affects Versions: 1.17.0
>Reporter: Charles Givre
>Assignee: luocong
>Priority: Major
> Labels: error_message_improvement
> Attachments: image-2020-01-26-16-47-46-398.png
>
>
> If you are attempting to create or update a storage plugin and for whatever
> reason an error occurs, the only error message that is displayed in the GUI
> is
> {code:java}
> Please retry: Error (unable to parse JSON)
> {code}
> This is unhelpful to the user as the user may have entered in valid JSON, but
> specified an invalid option. The error gives no indication as to what
> actually went wrong and how to fix.
> See example below:
> !image-2020-01-26-16-47-46-398.png!
> In this example, the cause of the error is the final option isMysql: false,
> which does not exist as a configuration option for the JDBC plugin.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (DRILL-7820) Not Supporting Mongo DB Name Capital Letters
[ https://issues.apache.org/jira/browse/DRILL-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong reassigned DRILL-7820: -- Assignee: luocong > Not Supporting Mongo DB Name Capital Letters > > > Key: DRILL-7820 > URL: https://issues.apache.org/jira/browse/DRILL-7820 > Project: Apache Drill > Issue Type: Bug > Components: Storage - MongoDB >Affects Versions: 1.17.0 >Reporter: RAJESH GUPTA >Assignee: luocong >Priority: Major > Fix For: 1.19.0 > > > Hi, > I successfully connected to Mongo DB using connection string and my mongo DB > has some DB name in Capital Letter like "HELLO" and some are small "test". > When I run show databases; command then it show all database but when I > execute > show tables; command using the "use mongo.HELLO" then don't show any tables > but when I execute same command using "use mongo.test" then it show all > tables. > And bot database has the same collections. > So, Apache Drill doesn't support if the mongo database name in Capital > Letters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (DRILL-7787) Apache drill failed to start
[ https://issues.apache.org/jira/browse/DRILL-7787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong resolved DRILL-7787. Fix Version/s: 1.18.0 Reviewer: Charles Givre Resolution: Fixed > Apache drill failed to start > > > Key: DRILL-7787 > URL: https://issues.apache.org/jira/browse/DRILL-7787 > Project: Apache Drill > Issue Type: Bug >Reporter: Om Prasad Surapu >Assignee: luocong >Priority: Major > Fix For: 1.19.0, 1.18.0 > > > Hi Team, > I have apache drill cluster setup with apache-drill-1.17.0 and started in > distributed mode (with zookeeper). Drill started and no issues reported. > > Have installed apache-drill-1.18.0 to fix DRILL-7786 but drill failed to > start with below exception. I have tried zookeeper version 3.5.8 and 3.4.11). > Could you help me out to fix this issue? > Exception in thread "main" > org.apache.drill.exec.exception.DrillbitStartupException: Failure during > initial startup of Drillbit. > at org.apache.drill.exec.server.Drillbit.start(Drillbit.java:588) > at org.apache.drill.exec.server.Drillbit.start(Drillbit.java:554) > at org.apache.drill.exec.server.Drillbit.main(Drillbit.java:550) > Caused by: org.apache.drill.common.exceptions.DrillRuntimeException: unable > to put > at > org.apache.drill.exec.coord.zk.ZookeeperClient.putIfAbsent(ZookeeperClient.java:326) > at > org.apache.drill.exec.store.sys.store.ZookeeperPersistentStore.putIfAbsent(ZookeeperPersistentStore.java:119) > at > org.apache.drill.exec.expr.fn.registry.RemoteFunctionRegistry.prepareStores(RemoteFunctionRegistry.java:201) > at > org.apache.drill.exec.expr.fn.registry.RemoteFunctionRegistry.init(RemoteFunctionRegistry.java:108) > at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:233) > at org.apache.drill.exec.server.Drillbit.start(Drillbit.java:584) > ... 2 more > Caused by: org.apache.zookeeper.KeeperException$UnimplementedException: > KeeperErrorCode = Unimplemented for /drill/udf/registry > at org.apache.zookeeper.KeeperException.create(KeeperException.java:106) > at org.apache.zookeeper.KeeperException.create(KeeperException.java:54) > at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1637) > at > org.apache.curator.framework.imps.CreateBuilderImpl$17.call(CreateBuilderImpl.java:1180) > at > org.apache.curator.framework.imps.CreateBuilderImpl$17.call(CreateBuilderImpl.java:1156) > at > org.apache.curator.connection.StandardConnectionHandlingPolicy.callWithRetry(StandardConnectionHandlingPolicy.java:67) > at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:81) > at > org.apache.curator.framework.imps.CreateBuilderImpl.pathInForeground(CreateBuilderImpl.java:1153) > at > org.apache.curator.framework.imps.CreateBuilderImpl.protectedPathInForeground(CreateBuilderImpl.java:607) > at > org.apache.curator.framework.imps.CreateBuilderImpl.forPath(CreateBuilderImpl.java:597) > at > org.apache.curator.framework.imps.CreateBuilderImpl.forPath(CreateBuilderImpl.java:51) > at > org.apache.drill.exec.coord.zk.ZookeeperClient.putIfAbsent(ZookeeperClient.java:318) > ... 7 more -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (DRILL-7525) Convert SequenceFiles to EVF
[ https://issues.apache.org/jira/browse/DRILL-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong reassigned DRILL-7525: -- Assignee: luocong (was: Arina Ielchiieva) > Convert SequenceFiles to EVF > > > Key: DRILL-7525 > URL: https://issues.apache.org/jira/browse/DRILL-7525 > Project: Apache Drill > Issue Type: Sub-task >Affects Versions: 1.17.0 >Reporter: Arina Ielchiieva >Assignee: luocong >Priority: Major > Fix For: 1.19.0 > > > Convert SequenceFiles to EVF -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (DRILL-7787) Apache drill failed to start
[ https://issues.apache.org/jira/browse/DRILL-7787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong reassigned DRILL-7787: -- Assignee: luocong > Apache drill failed to start > > > Key: DRILL-7787 > URL: https://issues.apache.org/jira/browse/DRILL-7787 > Project: Apache Drill > Issue Type: Bug >Reporter: Om Prasad Surapu >Assignee: luocong >Priority: Major > Fix For: 1.19.0 > > > Hi Team, > I have apache drill cluster setup with apache-drill-1.17.0 and started in > distributed mode (with zookeeper). Drill started and no issues reported. > > Have installed apache-drill-1.18.0 to fix DRILL-7786 but drill failed to > start with below exception. I have tried zookeeper version 3.5.8 and 3.4.11). > Could you help me out to fix this issue? > Exception in thread "main" > org.apache.drill.exec.exception.DrillbitStartupException: Failure during > initial startup of Drillbit. > at org.apache.drill.exec.server.Drillbit.start(Drillbit.java:588) > at org.apache.drill.exec.server.Drillbit.start(Drillbit.java:554) > at org.apache.drill.exec.server.Drillbit.main(Drillbit.java:550) > Caused by: org.apache.drill.common.exceptions.DrillRuntimeException: unable > to put > at > org.apache.drill.exec.coord.zk.ZookeeperClient.putIfAbsent(ZookeeperClient.java:326) > at > org.apache.drill.exec.store.sys.store.ZookeeperPersistentStore.putIfAbsent(ZookeeperPersistentStore.java:119) > at > org.apache.drill.exec.expr.fn.registry.RemoteFunctionRegistry.prepareStores(RemoteFunctionRegistry.java:201) > at > org.apache.drill.exec.expr.fn.registry.RemoteFunctionRegistry.init(RemoteFunctionRegistry.java:108) > at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:233) > at org.apache.drill.exec.server.Drillbit.start(Drillbit.java:584) > ... 2 more > Caused by: org.apache.zookeeper.KeeperException$UnimplementedException: > KeeperErrorCode = Unimplemented for /drill/udf/registry > at org.apache.zookeeper.KeeperException.create(KeeperException.java:106) > at org.apache.zookeeper.KeeperException.create(KeeperException.java:54) > at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1637) > at > org.apache.curator.framework.imps.CreateBuilderImpl$17.call(CreateBuilderImpl.java:1180) > at > org.apache.curator.framework.imps.CreateBuilderImpl$17.call(CreateBuilderImpl.java:1156) > at > org.apache.curator.connection.StandardConnectionHandlingPolicy.callWithRetry(StandardConnectionHandlingPolicy.java:67) > at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:81) > at > org.apache.curator.framework.imps.CreateBuilderImpl.pathInForeground(CreateBuilderImpl.java:1153) > at > org.apache.curator.framework.imps.CreateBuilderImpl.protectedPathInForeground(CreateBuilderImpl.java:607) > at > org.apache.curator.framework.imps.CreateBuilderImpl.forPath(CreateBuilderImpl.java:597) > at > org.apache.curator.framework.imps.CreateBuilderImpl.forPath(CreateBuilderImpl.java:51) > at > org.apache.drill.exec.coord.zk.ZookeeperClient.putIfAbsent(ZookeeperClient.java:318) > ... 7 more -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DRILL-7816) bootstrap-storage-plugins.json is an outdated example
[ https://issues.apache.org/jira/browse/DRILL-7816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luocong closed DRILL-7816. -- Reviewer: Charles Givre Resolution: Fixed > bootstrap-storage-plugins.json is an outdated example > - > > Key: DRILL-7816 > URL: https://issues.apache.org/jira/browse/DRILL-7816 > Project: Apache Drill > Issue Type: Bug > Components: Storage - JDBC >Affects Versions: 1.18.0 >Reporter: luocong >Assignee: luocong >Priority: Blocker > Fix For: 1.19.0 > > > I create the rdbms storage with the example plugin, get the below error > message. > org.apache.drill.common.exceptions.UserException: CONNECTION ERROR: Unable to > configure data source: Property maxIdle does not exist on target class > com.zaxxer.hikari.HikariConfig. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DRILL-7816) bootstrap-storage-plugins.json is an outdated example
luocong created DRILL-7816: -- Summary: bootstrap-storage-plugins.json is an outdated example Key: DRILL-7816 URL: https://issues.apache.org/jira/browse/DRILL-7816 Project: Apache Drill Issue Type: Bug Components: Storage - JDBC Affects Versions: 1.18.0 Reporter: luocong Fix For: 1.19.0 I create the rdbms storage with the example plugin, get the below error message. org.apache.drill.common.exceptions.UserException: CONNECTION ERROR: Unable to configure data source: Property maxIdle does not exist on target class com.zaxxer.hikari.HikariConfig. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DRILL-7815) 1.18 cannot connect to Hive 2.3 with embedded metastore
[
https://issues.apache.org/jira/browse/DRILL-7815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
luocong updated DRILL-7815:
---
Description:
Hi, I tested the compatibility of the 1.18 RC. As a result, Drill 1.18 can
still connect to HDFS 2.6 (Based CDH 5.13), but cannot connect to Hive 2.3. The
metadata of Hive 3.1 required by Drill 1.18 has changed a lot. This is the
official upgrade
script([https://github.com/apache/hive/blob/master/standalone-metastore/metastore-server/src/main/sql/mysql/upgrade-2.3.0-to-3.0.0.mysql.sql]).
Here are the errors thrown by trying to connect to Hive 2.3 with embedded
metastore. And then I also test the remote metastore, can be created
successfully, but don't show anything after "show databases".
{code:java}
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown
column 'CTLG_NAME' in 'field list'
at sun.reflect.GeneratedConstructorAccessor368.newInstance(Unknown
Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
{code}
was:
Hi, I tested the compatibility of the 1.18 RC. As a result, Drill 1.18 can
still connect to HDFS 2.6 (Based CDH 5.13), but cannot connect to Hive 2.3. The
metadata of Hive 3.1 required by Drill 1.18 has changed a lot. This is the
official upgrade
script([https://github.com/apache/hive/blob/master/standalone-metastore/metastore-server/src/main/sql/mysql/upgrade-2.3.0-to-3.0.0.mysql.sql]).
Here are the errors thrown by trying to connect to Hive 2.3 with embedded
metastore. And then I also test the remote metastore, can be created
successfully, but don't show anything after "show dadabases".
{code:java}
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown
column 'CTLG_NAME' in 'field list'
at sun.reflect.GeneratedConstructorAccessor368.newInstance(Unknown
Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
{code}
> 1.18 cannot connect to Hive 2.3 with embedded metastore
> ---
>
> Key: DRILL-7815
> URL: https://issues.apache.org/jira/browse/DRILL-7815
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Hive
>Affects Versions: 1.18.0
> Environment: Hive 2.3.7
>Reporter: luocong
>Priority: Major
>
> Hi, I tested the compatibility of the 1.18 RC. As a result, Drill 1.18 can
> still connect to HDFS 2.6 (Based CDH 5.13), but cannot connect to Hive 2.3.
> The metadata of Hive 3.1 required by Drill 1.18 has changed a lot. This is
> the official upgrade
> script([https://github.com/apache/hive/blob/master/standalone-metastore/metastore-server/src/main/sql/mysql/upgrade-2.3.0-to-3.0.0.mysql.sql]).
> Here are the errors thrown by trying to connect to Hive 2.3 with embedded
> metastore. And then I also test the remote metastore, can be created
> successfully, but don't show anything after "show databases".
> {code:java}
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown
> column 'CTLG_NAME' in 'field list'
> at sun.reflect.GeneratedConstructorAccessor368.newInstance(Unknown
> Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (DRILL-7815) 1.18 cannot connect to Hive 2.3 with embedded metastore
luocong created DRILL-7815:
--
Summary: 1.18 cannot connect to Hive 2.3 with embedded metastore
Key: DRILL-7815
URL: https://issues.apache.org/jira/browse/DRILL-7815
Project: Apache Drill
Issue Type: Bug
Components: Storage - Hive
Affects Versions: 1.18.0
Environment: Hive 2.3.7
Reporter: luocong
Hi, I tested the compatibility of the 1.18 RC. As a result, Drill 1.18 can
still connect to HDFS 2.6 (Based CDH 5.13), but cannot connect to Hive 2.3. The
metadata of Hive 3.1 required by Drill 1.18 has changed a lot. This is the
official upgrade
script([https://github.com/apache/hive/blob/master/standalone-metastore/metastore-server/src/main/sql/mysql/upgrade-2.3.0-to-3.0.0.mysql.sql]).
Here are the errors thrown by trying to connect to Hive 2.3 with embedded
metastore. And then I also test the remote metastore, can be created
successfully, but don't show anything after "show dadabases".
{code:java}
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown
column 'CTLG_NAME' in 'field list'
at sun.reflect.GeneratedConstructorAccessor368.newInstance(Unknown
Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
