You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Chun Chang (JIRA)" <ji...@apache.org> on 2017/10/18 22:05:00 UTC
[jira] [Commented] (DRILL-4511) refresh over empty folder results
in error, we need a better error message
[ https://issues.apache.org/jira/browse/DRILL-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210122#comment-16210122 ]
Chun Chang commented on DRILL-4511:
-----------------------------------
0: jdbc:drill:zk=10.10.30.166:5181> refresh table metadata dfs.`/drill/testdata/empty`;
+--------+----------------------------------------------+
| ok | summary |
+--------+----------------------------------------------+
| false | Table /drill/testdata/empty does not exist. |
+--------+----------------------------------------------+
> refresh over empty folder results in error, we need a better error message
> --------------------------------------------------------------------------
>
> Key: DRILL-4511
> URL: https://issues.apache.org/jira/browse/DRILL-4511
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Parquet
> Affects Versions: 1.7.0
> Reporter: Khurram Faraaz
> Assignee: Roman Kulyk
> Labels: ready-to-commit
> Fix For: 1.11.0
>
>
> refresh table metadata <empty-folder> results in error on sqlline prompt. We need a better message on sqlline prompt, something like, "The folder is empty, and there is no metadata to refresh"
> [root@centos-01 ~]# hadoop fs -ls /tmp
> ...
> drwxr-xr-x - root root 0 2015-07-21 21:16 /tmp/complex
> ...
> {noformat}
> 0: jdbc:drill:schema=dfs.tmp> refresh table metadata complex;
> +--------+--------------+
> | ok | summary |
> +--------+--------------+
> | false | Error: null |
> +--------+--------------+
> 1 row selected (0.131 seconds)
> {noformat}
> Stack trace from drillbit.log
> {noformat}
> 2016-03-15 10:50:23,747 [2918170f-84ee-a6fb-38eb-266108bd64f3:foreman] INFO o.a.drill.exec.work.foreman.Foreman - Query text for query id 2918170f-84ee-a6fb-38eb-266108bd64f3: refresh table metadata complex
> 2016-03-15 10:50:23,790 [2918170f-84ee-a6fb-38eb-266108bd64f3:foreman] ERROR o.a.d.e.p.s.h.RefreshMetadataHandler - Failed to update metadata for table 'complex'
> java.lang.NullPointerException: null
> at org.apache.drill.exec.store.dfs.FileSelection.minusDirectories(FileSelection.java:153) ~[drill-java-exec-1.7.0-SNAPSHOT.jar:1.7.0-SNAPSHOT]
> at org.apache.drill.exec.store.dfs.WorkspaceSchemaFactory$WorkspaceSchema.create(WorkspaceSchemaFactory.java:594) ~[drill-java-exec-1.7.0-SNAPSHOT.jar:1.7.0-SNAPSHOT]
> at org.apache.drill.exec.store.dfs.WorkspaceSchemaFactory$WorkspaceSchema.create(WorkspaceSchemaFactory.java:370) ~[drill-java-exec-1.7.0-SNAPSHOT.jar:1.7.0-SNAPSHOT]
> at org.apache.drill.exec.planner.sql.ExpandingConcurrentMap.getNewEntry(ExpandingConcurrentMap.java:96) ~[drill-java-exec-1.7.0-SNAPSHOT.jar:1.7.0-SNAPSHOT]
> at org.apache.drill.exec.planner.sql.ExpandingConcurrentMap.get(ExpandingConcurrentMap.java:90) ~[drill-java-exec-1.7.0-SNAPSHOT.jar:1.7.0-SNAPSHOT]
> at org.apache.drill.exec.store.dfs.WorkspaceSchemaFactory$WorkspaceSchema.getTable(WorkspaceSchemaFactory.java:524) ~[drill-java-exec-1.7.0-SNAPSHOT.jar:1.7.0-SNAPSHOT]
> at org.apache.calcite.jdbc.SimpleCalciteSchema.getTable(SimpleCalciteSchema.java:82) ~[calcite-core-1.4.0-drill-r10.jar:1.4.0-drill-r10]
> at org.apache.calcite.jdbc.CalciteAbstractSchema$SchemaPlusImpl.getTable(CalciteAbstractSchema.java:177) ~[calcite-core-1.4.0-drill-r10.jar:1.4.0-drill-r10]
> at org.apache.drill.exec.planner.sql.handlers.RefreshMetadataHandler.getPlan(RefreshMetadataHandler.java:73) ~[drill-java-exec-1.7.0-SNAPSHOT.jar:1.7.0-SNAPSHOT]
> at org.apache.drill.exec.planner.sql.DrillSqlWorker.getPlan(DrillSqlWorker.java:94) [drill-java-exec-1.7.0-SNAPSHOT.jar:1.7.0-SNAPSHOT]
> at org.apache.drill.exec.work.foreman.Foreman.runSQL(Foreman.java:927) [drill-java-exec-1.7.0-SNAPSHOT.jar:1.7.0-SNAPSHOT]
> at org.apache.drill.exec.work.foreman.Foreman.run(Foreman.java:251) [drill-java-exec-1.7.0-SNAPSHOT.jar:1.7.0-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_45]
> at java.lang.Thread.run(Thread.java:744) [na:1.7.0_45]
> 2016-03-15 10:50:23,801 [2918170f-84ee-a6fb-38eb-266108bd64f3:frag:0:0] INFO o.a.d.e.w.fragment.FragmentExecutor - 2918170f-84ee-a6fb-38eb-266108bd64f3:0:0: State change requested AWAITING_ALLOCATION --> RUNNING
> 2016-03-15 10:50:23,801 [2918170f-84ee-a6fb-38eb-266108bd64f3:frag:0:0] INFO o.a.d.e.w.f.FragmentStatusReporter - 2918170f-84ee-a6fb-38eb-266108bd64f3:0:0: State to report: RUNNING
> 2016-03-15 10:50:23,808 [2918170f-84ee-a6fb-38eb-266108bd64f3:frag:0:0] INFO o.a.d.e.w.fragment.FragmentExecutor - 2918170f-84ee-a6fb-38eb-266108bd64f3:0:0: State change requested RUNNING --> FINISHED
> 2016-03-15 10:50:23,808 [2918170f-84ee-a6fb-38eb-266108bd64f3:frag:0:0] INFO o.a.d.e.w.f.FragmentStatusReporter - 2918170f-84ee-a6fb-38eb-266108bd64f3:0:0: State to report: FINISHED
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)