[jira] [Assigned] (DRILL-5775) Select * query on a maprdb binary table fails

[ https://issues.apache.org/jira/browse/DRILL-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-5775: - Assignee: Jinfeng Ni > Select * query on a maprdb binary table fails >

[jira] [Commented] (DRILL-5532) TPCH Query 16 failed when planner.width.max_per_node <10

[ https://issues.apache.org/jira/browse/DRILL-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16163928#comment-16163928 ] Jinfeng Ni commented on DRILL-5532: --- This seems to be exposing a problem in execution time, after the

[jira] [Commented] (DRILL-1162) 25 way join ended up with OOM

[ https://issues.apache.org/jira/browse/DRILL-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160233#comment-16160233 ] Jinfeng Ni commented on DRILL-1162: --- This OOM problem exposes two problems. The first one is in planning

[jira] [Commented] (DRILL-5769) IndexOutOfBoundsException when querying JSON files

[ https://issues.apache.org/jira/browse/DRILL-5769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157872#comment-16157872 ] Jinfeng Ni commented on DRILL-5769: --- In JSON dataset, `assetData.debt.couponPaymentFeature` is an array

[jira] [Commented] (DRILL-5769) IndexOutOfBoundsException when querying JSON files

[ https://issues.apache.org/jira/browse/DRILL-5769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157860#comment-16157860 ] Jinfeng Ni commented on DRILL-5769: --- I can reproduce this problem with the following options (the

[jira] [Created] (DRILL-5773) Project pushdown into a subquery with select *

Jinfeng Ni created DRILL-5773: - Summary: Project pushdown into a subquery with select * Key: DRILL-5773 URL: https://issues.apache.org/jira/browse/DRILL-5773 Project: Apache Drill Issue Type:

[jira] [Assigned] (DRILL-5769) IndexOutOfBoundsException when querying JSON files

[ https://issues.apache.org/jira/browse/DRILL-5769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-5769: - Assignee: Jinfeng Ni > IndexOutOfBoundsException when querying JSON files >

[jira] [Commented] (DRILL-5769) IndexOutOfBoundsException when querying JSON files

[ https://issues.apache.org/jira/browse/DRILL-5769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154562#comment-16154562 ] Jinfeng Ni commented on DRILL-5769: --- Thanks for providing the reproduce sample dataset. I'll take a

[jira] [Commented] (DRILL-4255) SELECT DISTINCT query over JSON data returns UNSUPPORTED OPERATION

[ https://issues.apache.org/jira/browse/DRILL-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154488#comment-16154488 ] Jinfeng Ni commented on DRILL-4255: --- I think this issue was fixed by patch for DRILL-5546, commit id

[jira] [Resolved] (DRILL-4255) SELECT DISTINCT query over JSON data returns UNSUPPORTED OPERATION

[ https://issues.apache.org/jira/browse/DRILL-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-4255. --- Resolution: Fixed Fix Version/s: 1.12.0 > SELECT DISTINCT query over JSON data returns

[jira] [Resolved] (DRILL-4686) Aggregation query over HBase table results in IllegalStateException: Failure while reading vector

[ https://issues.apache.org/jira/browse/DRILL-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-4686. --- Resolution: Fixed Fix Version/s: 1.12.0 Fixed as part of patch for DRILL-5546. commit id :

[jira] [Resolved] (DRILL-4734) Query against HBase table on a 5 node cluster fails with SchemaChangeException

[ https://issues.apache.org/jira/browse/DRILL-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-4734. --- Resolution: Fixed Fix Version/s: 1.12.0 Although I could not get enough information to

[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=16154477#comment-16154477 ] Jinfeng Ni commented on DRILL-5185: --- Run against commit id : fde0a1df1734e0742b49aabdd28b02202ee2b044.

[jira] [Resolved] (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 resolved DRILL-5185. --- Resolution: Fixed Fix Version/s: 1.12.0 Fixed as part of DRILL-5546. Commit id:

[jira] [Resolved] (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:all-tabpanel ] Jinfeng Ni resolved DRILL-5464. --- Resolution: Fixed Fix Version/s: 1.12.0 Fixed as a part of patch for DRILL-5546, commit id:

[jira] [Resolved] (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 resolved DRILL-5327. --- Resolution: Fixed Fix Version/s: 1.12.0 Fixed as part of patch for DRILL-5546. Commit id:

[jira] [Comment Edited] (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=16154461#comment-16154461 ] Jinfeng Ni edited comment on DRILL-5327 at 9/5/17 10:18 PM: I run tpcds

[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=16154461#comment-16154461 ] Jinfeng Ni commented on DRILL-5327: --- I run tpcds query66 on scale factor 1 parquet dataset in a 2-node

[jira] [Resolved] (DRILL-5480) Empty batch returning from HBase may cause SchemChangeException even when data does not have different schema

[ https://issues.apache.org/jira/browse/DRILL-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-5480. --- Resolution: Fixed Fix Version/s: 1.12.0 Mark it resolved, as the issue was fixed as part of

[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=16154452#comment-16154452 ] Jinfeng Ni commented on DRILL-5480: --- Run the above two queries on the patch of DRILL-5546, commit id:

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

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

[jira] [Created] (DRILL-5768) Drill planer should not allow select * with group by clause

Jinfeng Ni created DRILL-5768: - Summary: Drill planer should not allow select * with group by clause Key: DRILL-5768 URL: https://issues.apache.org/jira/browse/DRILL-5768 Project: Apache Drill

[jira] [Created] (DRILL-5754) Test framework does not enforce column orders

Jinfeng Ni created DRILL-5754: - Summary: Test framework does not enforce column orders Key: DRILL-5754 URL: https://issues.apache.org/jira/browse/DRILL-5754 Project: Apache Drill Issue Type: Bug

[jira] [Created] (DRILL-5747) Drill should put directory name field in same sequence w.r.t regular column for select * query

Jinfeng Ni created DRILL-5747: - Summary: Drill should put directory name field in same sequence w.r.t regular column for select * query Key: DRILL-5747 URL: https://issues.apache.org/jira/browse/DRILL-5747

[jira] [Resolved] (DRILL-5685) Provide a way to set common environment variable between sqlline and Drillbit differently.

[ https://issues.apache.org/jira/browse/DRILL-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-5685. --- Resolution: Fixed Fixed in ae123e166af2ddb22c79b8cb93278a66fccc3be4 > Provide a way to set common

[jira] [Commented] (DRILL-5712) Update the pom files with dependency exclusions for commons-codec

[ https://issues.apache.org/jira/browse/DRILL-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126810#comment-16126810 ] Jinfeng Ni commented on DRILL-5712: --- Some of the unit testcases that failed: Tests in error:

[jira] [Commented] (DRILL-5712) Update the pom files with dependency exclusions for commons-codec

[ https://issues.apache.org/jira/browse/DRILL-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126808#comment-16126808 ] Jinfeng Ni commented on DRILL-5712: --- I'm seeing both failures in unit test and functional regression

[jira] [Reopened] (DRILL-5685) Provide a way to set common environment variable between sqlline and Drillbit differently.

[ https://issues.apache.org/jira/browse/DRILL-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reopened DRILL-5685: --- > Provide a way to set common environment variable between sqlline and Drillbit > differently. >

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

[ https://issues.apache.org/jira/browse/DRILL-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-4735: -- Labels: ready-to-commit (was: ) > Count(dir0) on parquet returns 0 result >

[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=16115154#comment-16115154 ] Jinfeng Ni commented on DRILL-5546: --- I have a work-in-progress branch. Tried the various of failed

[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=16115149#comment-16115149 ] Jinfeng Ni commented on DRILL-5327: --- I run tpcds- q66 on tpcds-sf1 text dataset on 1.11.0 on a cluster

[jira] [Comment Edited] (DRILL-4686) Aggregation query over HBase table results in IllegalStateException: Failure while reading vector

[ https://issues.apache.org/jira/browse/DRILL-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115140#comment-16115140 ] Jinfeng Ni edited comment on DRILL-4686 at 8/5/17 12:01 AM: I was able to

[jira] [Commented] (DRILL-4686) Aggregation query over HBase table results in IllegalStateException: Failure while reading vector

[ https://issues.apache.org/jira/browse/DRILL-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115140#comment-16115140 ] Jinfeng Ni commented on DRILL-4686: --- I was able to reproduce the problem on 1.11.0. With the patch for

[jira] [Commented] (DRILL-4255) SELECT DISTINCT query over JSON data returns UNSUPPORTED OPERATION

[ https://issues.apache.org/jira/browse/DRILL-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115103#comment-16115103 ] Jinfeng Ni commented on DRILL-4255: --- Seems to me the issues is same as DRILL-5464; the distinct clause

[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=16115068#comment-16115068 ] Jinfeng Ni commented on DRILL-5185: --- Run against a patch for DRILL-5466. The query, which originally

[jira] [Comment Edited] (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=16115064#comment-16115064 ] Jinfeng Ni edited comment on DRILL-5464 at 8/4/17 10:52 PM: Run the above

[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=16115064#comment-16115064 ] Jinfeng Ni commented on DRILL-5464: --- Run the above query with the patch for DRILL-5546, the umbrella

[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=16114919#comment-16114919 ] Jinfeng Ni commented on DRILL-5480: --- I have a branch to address the umbrella jira DRILL-5546. Tried the

[jira] [Commented] (DRILL-5696) change default compiler strategy

[ https://issues.apache.org/jira/browse/DRILL-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108069#comment-16108069 ] Jinfeng Ni commented on DRILL-5696: --- Can you provide more specific detail about the comparison you did?

[jira] [Commented] (DRILL-1162) 25 way join ended up with OOM

[ https://issues.apache.org/jira/browse/DRILL-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099190#comment-16099190 ] Jinfeng Ni commented on DRILL-1162: --- {quote} I found that in many cases right operator of hash join is

[jira] [Commented] (DRILL-1162) 25 way join ended up with OOM

[ https://issues.apache.org/jira/browse/DRILL-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099172#comment-16099172 ] Jinfeng Ni commented on DRILL-1162: --- Let me explain a little of background about DRILL-2236. DRILL-2236

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

[ https://issues.apache.org/jira/browse/DRILL-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-5667: - Assignee: Jinfeng Ni > Project operator would change output field order if convertfromJSON is

[jira] [Assigned] (DRILL-5681) Incorrect query result when query uses star and correlated subquery

[ https://issues.apache.org/jira/browse/DRILL-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-5681: - Assignee: Jinfeng Ni > Incorrect query result when query uses star and correlated subquery >

[jira] [Assigned] (DRILL-5683) Incorrect query result when query uses NOT(IS NOT NULL) expression

[ https://issues.apache.org/jira/browse/DRILL-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-5683: - Assignee: Jinfeng Ni > Incorrect query result when query uses NOT(IS NOT NULL) expression >

[jira] [Updated] (DRILL-5683) Incorrect query result when query uses NOT(IS NOT NULL) expression

[ https://issues.apache.org/jira/browse/DRILL-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-5683: -- Description: The following repo was modified from a testcase provided by Arjun Rajan(ara...@mapr.com).

[jira] [Created] (DRILL-5683) Incorrect query result when query uses NOT(IS NOT NULL) expression

Jinfeng Ni created DRILL-5683: - Summary: Incorrect query result when query uses NOT(IS NOT NULL) expression Key: DRILL-5683 URL: https://issues.apache.org/jira/browse/DRILL-5683 Project: Apache Drill

[jira] [Commented] (DRILL-5681) Incorrect query result when query uses star and correlated subquery

[ https://issues.apache.org/jira/browse/DRILL-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095433#comment-16095433 ] Jinfeng Ni commented on DRILL-5681: --- The incorrect query result was caused by a wrong query plan, when

[jira] [Created] (DRILL-5681) Incorrect query result when query uses star and correlated subquery

Jinfeng Ni created DRILL-5681: - Summary: Incorrect query result when query uses star and correlated subquery Key: DRILL-5681 URL: https://issues.apache.org/jira/browse/DRILL-5681 Project: Apache Drill

[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=16090177#comment-16090177 ] Jinfeng Ni commented on DRILL-4735: --- [~arina], the proposal looks good to me. It's great that you went

[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=16086558#comment-16086558 ] Jinfeng Ni commented on DRILL-5468: --- [~amansinha100], thanks. I think Option 1 makes sense for 1.11.

[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=16086540#comment-16086540 ] Jinfeng Ni commented on DRILL-5468: --- Looks like we have a couple of options: - Option 1 : leave the

[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=16086530#comment-16086530 ] Jinfeng Ni commented on DRILL-5468: --- [~amansinha100], turns out that the reason Drill did not pick

[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=16084875#comment-16084875 ] Jinfeng Ni commented on DRILL-5660: --- I'm more concerned about backward compatibility : can Drill 1.11.0

[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=16084777#comment-16084777 ] Jinfeng Ni commented on DRILL-5660: --- I thought you are asking for change to make Drill1.10 work with the

[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=16084522#comment-16084522 ] Jinfeng Ni commented on DRILL-5468: --- [~amansinha100], you are right that the HAVING predicate {{having

[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=16084402#comment-16084402 ] Jinfeng Ni commented on DRILL-5547: --- I have not looked into the detail. I have a general question.

[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=16084373#comment-16084373 ] Jinfeng Ni commented on DRILL-5660: --- Correct me if I'm wrong. I thought the goal for parquet metadata is

[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=16084309#comment-16084309 ] Jinfeng Ni commented on DRILL-5468: --- The difference between the plan prior to DRILL-4678 and the plan on

[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=16083099#comment-16083099 ] Jinfeng Ni commented on DRILL-5468: --- The performance regression was caused by a plan change for TPCH

[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=16082600#comment-16082600 ] Jinfeng Ni commented on DRILL-5468: --- I'll start looking into this performance regression. It might be a

[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] [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] [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=16059962#comment-16059962 ] Jinfeng Ni commented on DRILL-5336: --- Such behavior is a result of using select * from a schema-on-read

[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=16052193#comment-16052193 ] Jinfeng Ni commented on DRILL-5211: --- My 2cents: I could understand the cause of direct memory

[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

[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

[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] [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=16047230#comment-16047230 ] Jinfeng Ni commented on DRILL-5538: --- I put some comments and analysis in CALCITE-1584. > Exclude

[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=16045083#comment-16045083 ] Jinfeng Ni commented on DRILL-5547: --- What discussed here seems to be initialization of system options in

[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=16037290#comment-16037290 ] Jinfeng Ni edited comment on DRILL-5546 at 6/5/17 6:40 PM: --- Thanks for putting a

[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=16037290#comment-16037290 ] Jinfeng Ni commented on DRILL-5546: --- Thanks for putting a set of form definitions of terms, which would

[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-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=16035827#comment-16035827 ] Jinfeng Ni commented on DRILL-5229: --- Committer is [~sudheeshkatkam] (lost the trace after rebasing).

[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=16035823#comment-16035823 ] Jinfeng Ni commented on DRILL-5356: --- Committer is [~sudheeshkatkam] (lost the trace after rebasing).

[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=16035821#comment-16035821 ] Jinfeng Ni commented on DRILL-5379: --- Committer is [~sudheeshkatkam] (lost the trace after rebasing).

[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=16035819#comment-16035819 ] Jinfeng Ni commented on DRILL-5481: --- Committer is [~sudheeshkatkam] (lost the trace after rebasing).

[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=16035816#comment-16035816 ] Jinfeng Ni commented on DRILL-5533: --- Committer is [~sudheeshkatkam] (lost the trace after rebasing).

[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=16035817#comment-16035817 ] Jinfeng Ni commented on DRILL-5512: --- Committer is [~sudheeshkatkam] (lost the trace after rebasing).

[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=16035221#comment-16035221 ] Jinfeng Ni commented on DRILL-5546: --- Thanks for reviewing the proposal. Some clarifications. 1. The

[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-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=16031982#comment-16031982 ] Jinfeng Ni commented on DRILL-5559: --- The build is today's master branch, with commit id : {code}

[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-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=16030337#comment-16030337 ] Jinfeng Ni commented on DRILL-5525: --- At least one issue has been opened for

[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=16029868#comment-16029868 ] Jinfeng Ni commented on DRILL-5538: --- Thanks for finding CALCITE-1584, [~arina]. It seems to make sense

[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=16029852#comment-16029852 ] Jinfeng Ni commented on DRILL-5556: --- When same columns appear twice in Select list, Drill choose to

[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=16029842#comment-16029842 ] Jinfeng Ni commented on DRILL-5556: --- Agreed with [~amansinha100] that *, * is correct in postgres. I

[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

[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=16029831#comment-16029831 ] Jinfeng Ni commented on DRILL-5537: --- Thanks for posting the explain plan output, [~arina]. That makes

[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=16026925#comment-16026925 ] Jinfeng Ni commented on DRILL-5537: --- >From the change made in the PR, I'm not clear how/why the query

[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=16026901#comment-16026901 ] Jinfeng Ni commented on DRILL-5546: --- Link to the proposal draft in google doc:

[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=16026896#comment-16026896 ] Jinfeng Ni commented on DRILL-5546: --- h2. Scope and Motivation Several Drill operators such as HashJoin,

[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-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=16026333#comment-16026333 ] Jinfeng Ni commented on DRILL-5542: --- Sounds like planner should differentiate "*" and implicit columns,

[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=16026333#comment-16026333 ] Jinfeng Ni edited comment on DRILL-5542 at 5/26/17 2:35 PM: Sounds like

[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] [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=16016659#comment-16016659 ] Jinfeng Ni commented on DRILL-5480: --- We may argue that in the above reproduce sample data, hbase table

[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=16016484#comment-16016484 ] Jinfeng Ni commented on DRILL-5464: --- The above failure is actually intermittent; it depends on the race

[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

[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=15998999#comment-15998999 ] Jinfeng Ni commented on DRILL-5327: --- As a side comment, this tpchds_sf1 query66 seems to hit an

[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=15998992#comment-15998992 ] Jinfeng Ni commented on DRILL-5327: --- If we turn on the experimental feature "union type", the query will

  1   2   3   4   5   6   7   8   9   >