[jira] [Commented] (DRILL-5384) Sort cannot directly access map members, causes a data copy

[ https://issues.apache.org/jira/browse/DRILL-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943659#comment-15943659 ] Jinfeng Ni commented on DRILL-5384: --- Tried your example data: {code} select t.`order`.id

[jira] [Commented] (DRILL-5384) Sort cannot directly access map members, causes a data copy

[ https://issues.apache.org/jira/browse/DRILL-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943669#comment-15943669 ] Jinfeng Ni commented on DRILL-5384: --- The reason Drill decides to put a project for "cust

[jira] [Comment Edited] (DRILL-5384) Sort cannot directly access map members, causes a data copy

[ https://issues.apache.org/jira/browse/DRILL-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943669#comment-15943669 ] Jinfeng Ni edited comment on DRILL-5384 at 3/27/17 5:19 PM: Th

[jira] [Commented] (DRILL-5384) Sort cannot directly access map members, causes a data copy

[ https://issues.apache.org/jira/browse/DRILL-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943772#comment-15943772 ] Jinfeng Ni commented on DRILL-5384: --- I guess the first case with text file is you are us

[jira] [Commented] (DRILL-5378) Put more information into SchemaChangeException when HashJoin hit SchemaChangeException

[ https://issues.apache.org/jira/browse/DRILL-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944219#comment-15944219 ] Jinfeng Ni commented on DRILL-5378: --- [~amansinha100], could you please help review this

[jira] [Updated] (DRILL-5378) Put more information into SchemaChangeException when HashJoin hit SchemaChangeException

[ https://issues.apache.org/jira/browse/DRILL-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-5378: -- Labels: ready-to-commit (was: ) > Put more information into SchemaChangeException when HashJoin hit >

[jira] [Resolved] (DRILL-5373) Drill JDBC error in the process of connection via SQuirrel: java.lang.NoClassDefFoundError: javax/validation/constraints/NotNull

[ https://issues.apache.org/jira/browse/DRILL-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-5373. --- Resolution: Fixed Fixed in commit d3718a62e2315a601615db8803cdfdcc3cedab82 > Drill JDBC error in the

[jira] [Updated] (DRILL-5327) Hash aggregate can return empty batch which can cause schema change exception

[ https://issues.apache.org/jira/browse/DRILL-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-5327: -- Attachment: 271dbe08-c725-8e82-b6ea-53e9dab64e8b.sys.drill Upload a query profile when query hit this sc

[jira] [Commented] (DRILL-5327) Hash aggregate can return empty batch which can cause schema change exception

[ https://issues.apache.org/jira/browse/DRILL-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960127#comment-15960127 ] Jinfeng Ni commented on DRILL-5327: --- This is the detailed schema change error message.

[jira] [Commented] (DRILL-5327) Hash aggregate can return empty batch which can cause schema change exception

[ https://issues.apache.org/jira/browse/DRILL-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963729#comment-15963729 ] Jinfeng Ni commented on DRILL-5327: --- The root cause of the problem seems to be in UnionA

[jira] [Commented] (DRILL-5140) Fix CompileException in run-time generated code when record batch has large number of fields.

[ https://issues.apache.org/jira/browse/DRILL-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985646#comment-15985646 ] Jinfeng Ni commented on DRILL-5140: --- I'm not sure how common it is to have a query with

[jira] [Commented] (DRILL-5140) Fix CompileException in run-time generated code when record batch has large number of fields.

[ https://issues.apache.org/jira/browse/DRILL-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987967#comment-15987967 ] Jinfeng Ni commented on DRILL-5140: --- [~vvysotskyi], seems to me DRILL-5164 falls into s

[jira] [Assigned] (DRILL-5459) Extend physical operator test framework to test mini plans consisting of multiple operators

[ https://issues.apache.org/jira/browse/DRILL-5459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-5459: - Assignee: Jinfeng Ni > Extend physical operator test framework to test mini plans consisting of

[jira] [Created] (DRILL-5459) Extend physical operator test framework to test mini plans consisting of multiple operators

Jinfeng Ni created DRILL-5459: - Summary: Extend physical operator test framework to test mini plans consisting of multiple operators Key: DRILL-5459 URL: https://issues.apache.org/jira/browse/DRILL-5459 P

[jira] [Updated] (DRILL-5459) Extend physical operator test framework to test mini plans consisting of multiple operators

[ https://issues.apache.org/jira/browse/DRILL-5459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-5459: -- Description: DRILL-4437 introduced a unit test framework to test a non-scan physical operator. A JSON r

[jira] [Assigned] (DRILL-5185) Union all not passing type info when the output contains 0 rows

[ https://issues.apache.org/jira/browse/DRILL-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-5185: - Assignee: Jinfeng Ni > Union all not passing type info when the output contains 0 rows >

[jira] [Commented] (DRILL-5185) Union all not passing type info when the output contains 0 rows

[ https://issues.apache.org/jira/browse/DRILL-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993884#comment-15993884 ] Jinfeng Ni commented on DRILL-5185: --- The root cause of DRILL-5185 is same as the cause o

[jira] [Created] (DRILL-5464) Fix JSON reader when it deals with empty file

Jinfeng Ni created DRILL-5464: - Summary: Fix JSON reader when it deals with empty file Key: DRILL-5464 URL: https://issues.apache.org/jira/browse/DRILL-5464 Project: Apache Drill Issue Type: Bug

[jira] [Commented] (DRILL-5469) Meaningless error message when trying to use a constant in an order by statement

[ https://issues.apache.org/jira/browse/DRILL-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995902#comment-15995902 ] Jinfeng Ni commented on DRILL-5469: --- This is because * is dynamically expanded in Drill'

[jira] [Comment Edited] (DRILL-5469) Meaningless error message when trying to use a constant in an order by statement

[ https://issues.apache.org/jira/browse/DRILL-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995902#comment-15995902 ] Jinfeng Ni edited comment on DRILL-5469 at 5/3/17 11:32 PM: Th

[jira] [Commented] (DRILL-5464) Fix JSON reader when it deals with empty file

[ https://issues.apache.org/jira/browse/DRILL-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995908#comment-15995908 ] Jinfeng Ni commented on DRILL-5464: --- One idea might be to enable an experimental feature

[jira] [Commented] (DRILL-5327) Hash aggregate can return empty batch which can cause schema change exception

[ https://issues.apache.org/jira/browse/DRILL-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998992#comment-15998992 ] Jinfeng Ni commented on DRILL-5327: --- If we turn on the experimental feature "union type"

[jira] [Commented] (DRILL-5327) Hash aggregate can return empty batch which can cause schema change exception

[ https://issues.apache.org/jira/browse/DRILL-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998999#comment-15998999 ] Jinfeng Ni commented on DRILL-5327: --- As a side comment, this tpchds_sf1 query66 seems to

[jira] [Created] (DRILL-5480) Empty batch returning from HBase may cause SchemChangeException or incorrect query result

Jinfeng Ni created DRILL-5480: - Summary: Empty batch returning from HBase may cause SchemChangeException or incorrect query result Key: DRILL-5480 URL: https://issues.apache.org/jira/browse/DRILL-5480 Pro

[jira] [Updated] (DRILL-5480) Empty batch returning from HBase may cause SchemChangeException or incorrect query result

[ https://issues.apache.org/jira/browse/DRILL-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-5480: -- Description: The following repo was provided by [~haozhu]. 1. Create a Hbase table with 4 regions {code

[jira] [Assigned] (DRILL-5480) Empty batch returning from HBase may cause SchemChangeException or incorrect query result

[ https://issues.apache.org/jira/browse/DRILL-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-5480: - Assignee: Jinfeng Ni > Empty batch returning from HBase may cause SchemChangeException or incorre

[jira] [Commented] (DRILL-5464) Fix JSON reader when it deals with empty file

[ https://issues.apache.org/jira/browse/DRILL-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016484#comment-16016484 ] Jinfeng Ni commented on DRILL-5464: --- The above failure is actually intermittent; it depe

[jira] [Commented] (DRILL-5480) Empty batch returning from HBase may cause SchemChangeException or incorrect query result

[ https://issues.apache.org/jira/browse/DRILL-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016659#comment-16016659 ] Jinfeng Ni commented on DRILL-5480: --- We may argue that in the above reproduce sample dat

[jira] [Comment Edited] (DRILL-5480) Empty batch returning from HBase may cause SchemChangeException or incorrect query result

[ https://issues.apache.org/jira/browse/DRILL-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016659#comment-16016659 ] Jinfeng Ni edited comment on DRILL-5480 at 5/18/17 11:37 PM: -

[jira] [Commented] (DRILL-5480) Empty batch returning from HBase may cause SchemChangeException or incorrect query result

[ https://issues.apache.org/jira/browse/DRILL-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016674#comment-16016674 ] Jinfeng Ni commented on DRILL-5480: --- Another case where hbase has 3 regions with the las

[jira] [Created] (DRILL-5542) Scan unnecessary adds implicit columns to ScanRecordBatch for select * query

Jinfeng Ni created DRILL-5542: - Summary: Scan unnecessary adds implicit columns to ScanRecordBatch for select * query Key: DRILL-5542 URL: https://issues.apache.org/jira/browse/DRILL-5542 Project: Apache

[jira] [Comment Edited] (DRILL-5542) Scan unnecessary adds implicit columns to ScanRecordBatch for select * query

[ https://issues.apache.org/jira/browse/DRILL-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026333#comment-16026333 ] Jinfeng Ni edited comment on DRILL-5542 at 5/26/17 2:35 PM: So

[jira] [Commented] (DRILL-5542) Scan unnecessary adds implicit columns to ScanRecordBatch for select * query

[ https://issues.apache.org/jira/browse/DRILL-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026333#comment-16026333 ] Jinfeng Ni commented on DRILL-5542: --- Sounds like planner should differentiate "*" and im

[jira] [Updated] (DRILL-5140) Fix CompileException in run-time generated code when record batch has large number of fields.

[ https://issues.apache.org/jira/browse/DRILL-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-5140: -- Labels: ready-to-commit (was: ) > Fix CompileException in run-time generated code when record batch has

[jira] [Created] (DRILL-5546) Schema change problems caused by empty batch

Jinfeng Ni created DRILL-5546: - Summary: Schema change problems caused by empty batch Key: DRILL-5546 URL: https://issues.apache.org/jira/browse/DRILL-5546 Project: Apache Drill Issue Type: Bug

[jira] [Commented] (DRILL-5546) Schema change problems caused by empty batch

[ https://issues.apache.org/jira/browse/DRILL-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026896#comment-16026896 ] Jinfeng Ni commented on DRILL-5546: --- h2. Scope and Motivation Several Drill operators s

[jira] [Commented] (DRILL-5546) Schema change problems caused by empty batch

[ https://issues.apache.org/jira/browse/DRILL-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026901#comment-16026901 ] Jinfeng Ni commented on DRILL-5546: --- Link to the proposal draft in google doc: https://

[jira] [Commented] (DRILL-5537) Display columns alias for queries with sum() when RDBMS storage plugin is enabled

[ https://issues.apache.org/jira/browse/DRILL-5537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026925#comment-16026925 ] Jinfeng Ni commented on DRILL-5537: --- >From the change made in the PR, I'm not clear how/

[jira] [Commented] (DRILL-5537) Display columns alias for queries with sum() when RDBMS storage plugin is enabled

[ https://issues.apache.org/jira/browse/DRILL-5537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029831#comment-16029831 ] Jinfeng Ni commented on DRILL-5537: --- Thanks for posting the explain plan output, [~arina

[jira] [Updated] (DRILL-5537) Display columns alias for queries with sum() when RDBMS storage plugin is enabled

[ https://issues.apache.org/jira/browse/DRILL-5537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-5537: -- Labels: ready-to-commit (was: ) > Display columns alias for queries with sum() when RDBMS storage plugi

[jira] [Commented] (DRILL-5556) Drill allows "SELECT *, *" query

[ https://issues.apache.org/jira/browse/DRILL-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029842#comment-16029842 ] Jinfeng Ni commented on DRILL-5556: --- Agreed with [~amansinha100] that *, * is correct in

[jira] [Commented] (DRILL-5556) Drill allows "SELECT *, *" query

[ https://issues.apache.org/jira/browse/DRILL-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029852#comment-16029852 ] Jinfeng Ni commented on DRILL-5556: --- When same columns appear twice in Select list, Dril

[jira] [Commented] (DRILL-5538) Exclude ProjectRemoveRule during PHYSICAL phase if it comes from storage plugins

[ https://issues.apache.org/jira/browse/DRILL-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029868#comment-16029868 ] Jinfeng Ni commented on DRILL-5538: --- Thanks for finding CALCITE-1584, [~arina]. It seem

[jira] [Commented] (DRILL-5525) Inconsistent, unhelpful semantics for batch, field schema comparison

[ https://issues.apache.org/jira/browse/DRILL-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030337#comment-16030337 ] Jinfeng Ni commented on DRILL-5525: --- At least one issue has been opened for BatchSchema/

[jira] [Created] (DRILL-5559) Incorrect query result when querying json files with schema change

Jinfeng Ni created DRILL-5559: - Summary: Incorrect query result when querying json files with schema change Key: DRILL-5559 URL: https://issues.apache.org/jira/browse/DRILL-5559 Project: Apache Drill

[jira] [Commented] (DRILL-5559) Incorrect query result when querying json files with schema change

[ https://issues.apache.org/jira/browse/DRILL-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031982#comment-16031982 ] Jinfeng Ni commented on DRILL-5559: --- The build is today's master branch, with commit id

[jira] [Updated] (DRILL-5485) Remove WebServer dependency on DrillClient

[ https://issues.apache.org/jira/browse/DRILL-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-5485: -- Labels: ready-to-commit (was: ) > Remove WebServer dependency on DrillClient >

[jira] [Commented] (DRILL-5546) Schema change problems caused by empty batch

[ https://issues.apache.org/jira/browse/DRILL-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035221#comment-16035221 ] Jinfeng Ni commented on DRILL-5546: --- Thanks for reviewing the proposal. Some clarifica

[jira] [Commented] (DRILL-5512) Standardize error handling in ScanBatch

[ https://issues.apache.org/jira/browse/DRILL-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035817#comment-16035817 ] Jinfeng Ni commented on DRILL-5512: --- Committer is [~sudheeshkatkam] (lost the trace afte

[jira] [Commented] (DRILL-5533) Fix flag assignment in FunctionInitializer.checkInit() method

[ https://issues.apache.org/jira/browse/DRILL-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035816#comment-16035816 ] Jinfeng Ni commented on DRILL-5533: --- Committer is [~sudheeshkatkam] (lost the trace afte

[jira] [Commented] (DRILL-5481) Allow Drill to persist profiles in-memory only with a max capacity

[ https://issues.apache.org/jira/browse/DRILL-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035819#comment-16035819 ] Jinfeng Ni commented on DRILL-5481: --- Committer is [~sudheeshkatkam] (lost the trace afte

[jira] [Commented] (DRILL-5379) Set Hdfs Block Size based on Parquet Block Size

[ https://issues.apache.org/jira/browse/DRILL-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035821#comment-16035821 ] Jinfeng Ni commented on DRILL-5379: --- Committer is [~sudheeshkatkam] (lost the trace afte

[jira] [Commented] (DRILL-5356) Refactor Parquet Record Reader

[ https://issues.apache.org/jira/browse/DRILL-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035823#comment-16035823 ] Jinfeng Ni commented on DRILL-5356: --- Committer is [~sudheeshkatkam] (lost the trace afte

[jira] [Commented] (DRILL-5229) Upgrade kudu client to org.apache.kudu:kudu-client:1.2.0

[ https://issues.apache.org/jira/browse/DRILL-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035827#comment-16035827 ] Jinfeng Ni commented on DRILL-5229: --- Committer is [~sudheeshkatkam] (lost the trace afte

[jira] [Resolved] (DRILL-5485) Remove WebServer dependency on DrillClient

[ https://issues.apache.org/jira/browse/DRILL-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-5485. --- Resolution: Fixed Fixed in 874bf6296dcd1a42c7cf7f097c1a6b5458010cbb > Remove WebServer dependency on

[jira] [Commented] (DRILL-5546) Schema change problems caused by empty batch

[ https://issues.apache.org/jira/browse/DRILL-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037290#comment-16037290 ] Jinfeng Ni commented on DRILL-5546: --- Thanks for putting a set of form definitions of ter

[jira] [Comment Edited] (DRILL-5546) Schema change problems caused by empty batch

[ https://issues.apache.org/jira/browse/DRILL-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037290#comment-16037290 ] Jinfeng Ni edited comment on DRILL-5546 at 6/5/17 6:40 PM: --- Than

[jira] [Commented] (DRILL-5547) Drill config options and session options do not work as intended

[ https://issues.apache.org/jira/browse/DRILL-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045083#comment-16045083 ] Jinfeng Ni commented on DRILL-5547: --- What discussed here seems to be initialization of s

[jira] [Assigned] (DRILL-5581) Query with CASE statement returns wrong results

[ https://issues.apache.org/jira/browse/DRILL-5581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-5581: - Assignee: Jinfeng Ni > Query with CASE statement returns wrong results >

[jira] [Commented] (DRILL-5538) Exclude ProjectRemoveRule during PHYSICAL phase if it comes from storage plugins

[ https://issues.apache.org/jira/browse/DRILL-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047230#comment-16047230 ] Jinfeng Ni commented on DRILL-5538: --- I put some comments and analysis in CALCITE-1584.

[jira] [Created] (DRILL-5585) UnionAll operator generates run-time code for every incoming batch

Jinfeng Ni created DRILL-5585: - Summary: UnionAll operator generates run-time code for every incoming batch Key: DRILL-5585 URL: https://issues.apache.org/jira/browse/DRILL-5585 Project: Apache Drill

[jira] [Created] (DRILL-5586) UnionAll operator does more than necessary value vector allocation and copy

Jinfeng Ni created DRILL-5586: - Summary: UnionAll operator does more than necessary value vector allocation and copy Key: DRILL-5586 URL: https://issues.apache.org/jira/browse/DRILL-5586 Project: Apache D

[jira] [Assigned] (DRILL-5586) UnionAll operator does more than necessary value vector allocation and copy

[ https://issues.apache.org/jira/browse/DRILL-5586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-5586: - Assignee: Jinfeng Ni > UnionAll operator does more than necessary value vector allocation and cop

[jira] [Commented] (DRILL-5211) Queries fail due to direct memory fragmentation

[ https://issues.apache.org/jira/browse/DRILL-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052193#comment-16052193 ] Jinfeng Ni commented on DRILL-5211: --- My 2cents: I could understand the cause of direct

[jira] [Commented] (DRILL-5336) Columns returned by select over CTAS created parquet are not in correct order.

[ https://issues.apache.org/jira/browse/DRILL-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059962#comment-16059962 ] Jinfeng Ni commented on DRILL-5336: --- Such behavior is a result of using select * from a

[jira] [Updated] (DRILL-5165) wrong results - LIMIT ALL and OFFSET clause in same query

[ https://issues.apache.org/jira/browse/DRILL-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-5165: -- Labels: ready-to-commit (was: ) > wrong results - LIMIT ALL and OFFSET clause in same query > -

[jira] [Created] (DRILL-5667) Project operator would change output field order if convertfromJSON is used

Jinfeng Ni created DRILL-5667: - Summary: Project operator would change output field order if convertfromJSON is used Key: DRILL-5667 URL: https://issues.apache.org/jira/browse/DRILL-5667 Project: Apache

[jira] [Commented] (DRILL-5468) THCH Q18 regressed ~3x due to execution plan changes

[ https://issues.apache.org/jira/browse/DRILL-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082600#comment-16082600 ] Jinfeng Ni commented on DRILL-5468: --- I'll start looking into this performance regression

[jira] [Commented] (DRILL-5468) THCH Q18 regressed ~3x due to execution plan changes

[ https://issues.apache.org/jira/browse/DRILL-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083099#comment-16083099 ] Jinfeng Ni commented on DRILL-5468: --- The performance regression was caused by a plan cha

[jira] [Commented] (DRILL-5468) THCH Q18 regressed ~3x due to execution plan changes

[ https://issues.apache.org/jira/browse/DRILL-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084309#comment-16084309 ] Jinfeng Ni commented on DRILL-5468: --- The difference between the plan prior to DRILL-4678

[jira] [Commented] (DRILL-5660) Drill 1.10 queries fail due to Parquet Metadata "corruption" from DRILL-3867

[ https://issues.apache.org/jira/browse/DRILL-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084373#comment-16084373 ] Jinfeng Ni commented on DRILL-5660: --- Correct me if I'm wrong. I thought the goal for par

[jira] [Commented] (DRILL-5547) Drill config options and session options do not work as intended

[ https://issues.apache.org/jira/browse/DRILL-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084402#comment-16084402 ] Jinfeng Ni commented on DRILL-5547: --- I have not looked into the detail. I have a general

[jira] [Commented] (DRILL-5468) TPCH Q18 regressed ~3x due to execution plan changes

[ https://issues.apache.org/jira/browse/DRILL-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084522#comment-16084522 ] Jinfeng Ni commented on DRILL-5468: --- [~amansinha100], you are right that the HAVING pred

[jira] [Commented] (DRILL-5660) Drill 1.10 queries fail due to Parquet Metadata "corruption" from DRILL-3867

[ https://issues.apache.org/jira/browse/DRILL-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084777#comment-16084777 ] Jinfeng Ni commented on DRILL-5660: --- I thought you are asking for change to make Drill1.

[jira] [Commented] (DRILL-5660) Drill 1.10 queries fail due to Parquet Metadata "corruption" from DRILL-3867

[ https://issues.apache.org/jira/browse/DRILL-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084875#comment-16084875 ] Jinfeng Ni commented on DRILL-5660: --- I'm more concerned about backward compatibility : c

[jira] [Commented] (DRILL-5468) TPCH Q18 regressed ~3x due to execution plan changes

[ https://issues.apache.org/jira/browse/DRILL-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086530#comment-16086530 ] Jinfeng Ni commented on DRILL-5468: --- [~amansinha100], turns out that the reason Drill di

[jira] [Commented] (DRILL-5468) TPCH Q18 regressed ~3x due to execution plan changes

[ https://issues.apache.org/jira/browse/DRILL-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086540#comment-16086540 ] Jinfeng Ni commented on DRILL-5468: --- Looks like we have a couple of options: - Option 1

[jira] [Commented] (DRILL-5468) TPCH Q18 regressed ~3x due to execution plan changes

[ https://issues.apache.org/jira/browse/DRILL-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086558#comment-16086558 ] Jinfeng Ni commented on DRILL-5468: --- [~amansinha100], thanks. I think Option 1 makes sen

[jira] [Commented] (DRILL-4735) Count(dir0) on parquet returns 0 result

[ https://issues.apache.org/jira/browse/DRILL-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090177#comment-16090177 ] Jinfeng Ni commented on DRILL-4735: --- [~arina], the proposal looks good to me. It's great

[jira] [Commented] (DRILL-4467) Invalid projection created using PrelUtil.getColumns

[ https://issues.apache.org/jira/browse/DRILL-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180547#comment-15180547 ] Jinfeng Ni commented on DRILL-4467: --- I think the original plan is valid, although I agre

[jira] [Commented] (DRILL-4444) Window function query results in IllegalStateException

[ https://issues.apache.org/jira/browse/DRILL-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183121#comment-15183121 ] Jinfeng Ni commented on DRILL-: --- [~adeneche], you are right. The plan is not correct

[jira] [Commented] (DRILL-4474) Inconsistent behavior while using COUNT in select (Apache drill 1.2.0)

[ https://issues.apache.org/jira/browse/DRILL-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186144#comment-15186144 ] Jinfeng Ni commented on DRILL-4474: --- I submit a new PR, after putting a patch on top of

[jira] [Resolved] (DRILL-4474) Inconsistent behavior while using COUNT in select (Apache drill 1.2.0)

[ https://issues.apache.org/jira/browse/DRILL-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-4474. --- Resolution: Fixed Fix Version/s: 1.6.0 Fixed in commit: 49ae6d363efe78df4e89f7913d1d560e9627b32

[jira] [Commented] (DRILL-4474) Inconsistent behavior while using COUNT in select (Apache drill 1.2.0)

[ https://issues.apache.org/jira/browse/DRILL-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193681#comment-15193681 ] Jinfeng Ni commented on DRILL-4474: --- [~ssmane3], this patch will be included in the upco

[jira] [Resolved] (DRILL-4490) Count(*) function returns as optional instead of required

[ https://issues.apache.org/jira/browse/DRILL-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-4490. --- Resolution: Fixed Fix Version/s: 1.6.0 Fixed in commit: 46e3de790da8f9c6d2d18e7e40fd37c01b3b168

[jira] [Commented] (DRILL-4490) Count(*) function returns as optional instead of required

[ https://issues.apache.org/jira/browse/DRILL-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194313#comment-15194313 ] Jinfeng Ni commented on DRILL-4490: --- it's not in 1.6.0. It should be in 1.7.0 > Count(

[jira] [Resolved] (DRILL-4372) Drill Operators and Functions should correctly expose their types within Calcite

[ https://issues.apache.org/jira/browse/DRILL-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-4372. --- Resolution: Fixed Fix Version/s: 1.7.0 Fixed in commit: c0293354ec79b42ff27ce4ad2113a2ff52a934b

[jira] [Commented] (DRILL-2517) Apply Partition pruning before reading files during planning

[ https://issues.apache.org/jira/browse/DRILL-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204844#comment-15204844 ] Jinfeng Ni commented on DRILL-2517: --- No, it will not help in the case of parquet metadat

[jira] [Created] (DRILL-4531) Query with filter and aggregate hangs in planning phase

Jinfeng Ni created DRILL-4531: - Summary: Query with filter and aggregate hangs in planning phase Key: DRILL-4531 URL: https://issues.apache.org/jira/browse/DRILL-4531 Project: Apache Drill Issue

[jira] [Commented] (DRILL-4531) Query with filter and aggregate hangs in planning phase

[ https://issues.apache.org/jira/browse/DRILL-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209324#comment-15209324 ] Jinfeng Ni commented on DRILL-4531: --- Agreed. We should be able to timeout planning phas

[jira] [Assigned] (DRILL-3855) Enable FilterSetOpTransposeRule, DrillProjectSetOpTransposeRule

[ https://issues.apache.org/jira/browse/DRILL-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-3855: - Assignee: Jinfeng Ni > Enable FilterSetOpTransposeRule, DrillProjectSetOpTransposeRule >

[jira] [Created] (DRILL-4541) Make sure query planner does not generate operators with mixed convention trait

Jinfeng Ni created DRILL-4541: - Summary: Make sure query planner does not generate operators with mixed convention trait Key: DRILL-4541 URL: https://issues.apache.org/jira/browse/DRILL-4541 Project: Apac

[jira] [Resolved] (DRILL-4531) Query with filter and aggregate hangs in planning phase

[ https://issues.apache.org/jira/browse/DRILL-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-4531. --- Resolution: Fixed Fixed in commit: 7e6de2bbceffdb2566c57590da04113221f0a166 > Query with filter and a

[jira] [Comment Edited] (DRILL-4572) Column Alias Not Available in Subquery

[ https://issues.apache.org/jira/browse/DRILL-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222606#comment-15222606 ] Jinfeng Ni edited comment on DRILL-4572 at 4/2/16 1:00 AM: --- This

[jira] [Commented] (DRILL-4572) Column Alias Not Available in Subquery

[ https://issues.apache.org/jira/browse/DRILL-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222606#comment-15222606 ] Jinfeng Ni commented on DRILL-4572: --- This seems to be a bug in the query planner. I coul

[jira] [Commented] (DRILL-4572) Column Alias Not Available in Subquery

[ https://issues.apache.org/jira/browse/DRILL-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222608#comment-15222608 ] Jinfeng Ni commented on DRILL-4572: --- It might be related to the function used in the que

[jira] [Assigned] (DRILL-4541) Make sure query planner does not generate operators with mixed convention trait

[ https://issues.apache.org/jira/browse/DRILL-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-4541: - Assignee: Jinfeng Ni > Make sure query planner does not generate operators with mixed convention

[jira] [Created] (DRILL-4589) Reduce planning time for file system partition pruning by reducing filter evaluation overhead

Jinfeng Ni created DRILL-4589: - Summary: Reduce planning time for file system partition pruning by reducing filter evaluation overhead Key: DRILL-4589 URL: https://issues.apache.org/jira/browse/DRILL-4589

[jira] [Commented] (DRILL-4589) Reduce planning time for file system partition pruning by reducing filter evaluation overhead

[ https://issues.apache.org/jira/browse/DRILL-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229107#comment-15229107 ] Jinfeng Ni commented on DRILL-4589: --- This is related to DRILL-3759, which targets for mu

[jira] [Assigned] (DRILL-4589) Reduce planning time for file system partition pruning by reducing filter evaluation overhead

[ https://issues.apache.org/jira/browse/DRILL-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-4589: - Assignee: Jinfeng Ni > Reduce planning time for file system partition pruning by reducing filter

<    1   2   3   4   5   6   7   8   9   10   >