[jira] [Created] (DRILL-3316) Different SQLHandlers should go through the same planning logics.

Jinfeng Ni created DRILL-3316: - Summary: Different SQLHandlers should go through the same planning logics. Key: DRILL-3316 URL: https://issues.apache.org/jira/browse/DRILL-3316 Project: Apache Drill

[jira] [Assigned] (DRILL-3294) False schema change exception in CTAS with AVG window function

[ https://issues.apache.org/jira/browse/DRILL-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-3294: - Assignee: Jinfeng Ni (was: Chris Westin) > False schema change exception in CTAS with AVG window

[jira] [Updated] (DRILL-3294) False schema change exception in CTAS with AVG window function

[ https://issues.apache.org/jira/browse/DRILL-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-3294: -- Component/s: (was: Execution - Relational Operators) Query Planning & Optimization

[jira] [Updated] (DRILL-3294) False schema change exception in CTAS with AVG window function

[ https://issues.apache.org/jira/browse/DRILL-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-3294: -- Fix Version/s: 1.1.0 > False schema change exception in CTAS with AVG window function >

[jira] [Updated] (DRILL-2987) Inside an inner query : star should have been expanded (over CSV data)

[ https://issues.apache.org/jira/browse/DRILL-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2987: -- Fix Version/s: 1.2.0 > Inside an inner query : star should have been expanded (over CSV data) >

[jira] [Updated] (DRILL-2335) Error message must be updated to exclude unsupported operators when queries fail to parse

[ https://issues.apache.org/jira/browse/DRILL-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2335: -- Fix Version/s: (was: 1.1.0) Future > Error message must be updated to exclude uns

[jira] [Updated] (DRILL-1441) Replace sql function requires backticks to avoid parse error

[ https://issues.apache.org/jira/browse/DRILL-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-1441: -- Fix Version/s: (was: 1.1.0) Future > Replace sql function requires backticks to a

[jira] [Commented] (DRILL-3297) Using rank, dense_rank, percent_rank, cume_dist, row_number window functions without OVER clause results in cryptic schema change error

[ https://issues.apache.org/jira/browse/DRILL-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586764#comment-14586764 ] Jinfeng Ni commented on DRILL-3297: --- Window functions rank(), dense_ranK() etc must have

[jira] [Commented] (DRILL-1862) over clause with only order by clause throws an exception

[ https://issues.apache.org/jira/browse/DRILL-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582378#comment-14582378 ] Jinfeng Ni commented on DRILL-1862: --- +1. LGTM. > over clause with only order by cla

[jira] [Created] (DRILL-3248) Explain CTAS statement support

Jinfeng Ni created DRILL-3248: - Summary: Explain CTAS statement support Key: DRILL-3248 URL: https://issues.apache.org/jira/browse/DRILL-3248 Project: Apache Drill Issue Type: New Feature

[jira] [Created] (DRILL-3246) Query planning support for partition by clause in Drill's CTAS statement

Jinfeng Ni created DRILL-3246: - Summary: Query planning support for partition by clause in Drill's CTAS statement Key: DRILL-3246 URL: https://issues.apache.org/jira/browse/DRILL-3246 Project: Apache Dril

[jira] [Updated] (DRILL-3195) Throw unsupported exception for Window functions that are not currently supported

[ https://issues.apache.org/jira/browse/DRILL-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-3195: -- Assignee: Deneche A. Hakim (was: Jinfeng Ni) > Throw unsupported exception for Window functions that ar

[jira] [Commented] (DRILL-3004) Failure in planning join when disabling hash join and exchanges

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

[jira] [Updated] (DRILL-3004) Failure in planning join when disabling hash join and exchanges

[ https://issues.apache.org/jira/browse/DRILL-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-3004: -- Attachment: 0001-DRILL-3004-Fix-CanNotPlan-in-physical-planning-when-.patch > Failure in planning join w

[jira] [Updated] (DRILL-3173) Invalid inputs are NOT handled properly by Window functions

[ https://issues.apache.org/jira/browse/DRILL-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-3173: -- Assignee: Deneche A. Hakim (was: Jinfeng Ni) > Invalid inputs are NOT handled properly by Window functi

[jira] [Commented] (DRILL-2988) Correlated exists subquery returns wrong result if join columns in subquery are not fully qualified

[ https://issues.apache.org/jira/browse/DRILL-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556566#comment-14556566 ] Jinfeng Ni commented on DRILL-2988: --- We may argue why Postgres or other schema-aware sys

[jira] [Comment Edited] (DRILL-2988) Correlated exists subquery returns wrong result if join columns in subquery are not fully qualified

[ https://issues.apache.org/jira/browse/DRILL-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556504#comment-14556504 ] Jinfeng Ni edited comment on DRILL-2988 at 5/22/15 6:04 PM: I

[jira] [Commented] (DRILL-2988) Correlated exists subquery returns wrong result if join columns in subquery are not fully qualified

[ https://issues.apache.org/jira/browse/DRILL-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556504#comment-14556504 ] Jinfeng Ni commented on DRILL-2988: --- I think the naming resolutions are different in ca

[jira] [Updated] (DRILL-2967) Incompatible types error reported in a "not in" query with compatible data types

[ https://issues.apache.org/jira/browse/DRILL-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2967: -- Assignee: Sean Hsuan-Yi Chu (was: Jinfeng Ni) > Incompatible types error reported in a "not in" query w

[jira] [Updated] (DRILL-2967) Incompatible types error reported in a "not in" query with compatible data types

[ https://issues.apache.org/jira/browse/DRILL-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2967: -- Fix Version/s: 1.1.0 > Incompatible types error reported in a "not in" query with compatible data > typ

[jira] [Resolved] (DRILL-2346) Star is not expanded correctly in create view if view fields are specified

[ https://issues.apache.org/jira/browse/DRILL-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-2346. --- Resolution: Won't Fix Please re-open it if you feel this feature is strongly required. Otherwise, I t

[jira] [Commented] (DRILL-2346) Star is not expanded correctly in create view if view fields are specified

[ https://issues.apache.org/jira/browse/DRILL-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556372#comment-14556372 ] Jinfeng Ni commented on DRILL-2346: --- For now, I think this is the expected behavior. Fo

[jira] [Created] (DRILL-3156) Calcite tracing is broken in Drill

Jinfeng Ni created DRILL-3156: - Summary: Calcite tracing is broken in Drill Key: DRILL-3156 URL: https://issues.apache.org/jira/browse/DRILL-3156 Project: Apache Drill Issue Type: Bug

[jira] [Resolved] (DRILL-3044) Very deep record batch fetching stack for single table query (TestTpchLimit0.tpch01)

[ https://issues.apache.org/jira/browse/DRILL-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-3044. --- Resolution: Invalid As explained in previous comments, the plan looks to be normal. Please re-open i

[jira] [Updated] (DRILL-2958) Move Drill to alternative cost-based planner for Join planning

[ https://issues.apache.org/jira/browse/DRILL-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2958: -- Issue Type: New Feature (was: Bug) > Move Drill to alternative cost-based planner for Join planning > -

[jira] [Commented] (DRILL-3117) Wrong Join-Order when In-List is materialized as a table

[ https://issues.apache.org/jira/browse/DRILL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546571#comment-14546571 ] Jinfeng Ni commented on DRILL-3117: --- Why do you think the root cause of DRILL-2929 is sa

[jira] [Updated] (DRILL-3101) Setting "slice_target" to 1 changes the order of the columns in a "select *" query with order by

[ https://issues.apache.org/jira/browse/DRILL-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-3101: -- Assignee: Chris Westin (was: Jinfeng Ni) > Setting "slice_target" to 1 changes the order of the columns

[jira] [Updated] (DRILL-3101) Setting "slice_target" to 1 changes the order of the columns in a "select *" query with order by

[ https://issues.apache.org/jira/browse/DRILL-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-3101: -- Component/s: (was: Query Planning & Optimization) Execution - Relational Operators

[jira] [Resolved] (DRILL-3101) Setting "slice_target" to 1 changes the order of the columns in a "select *" query with order by

[ https://issues.apache.org/jira/browse/DRILL-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-3101. --- Resolution: Duplicate > Setting "slice_target" to 1 changes the order of the columns in a "select *"

[jira] [Commented] (DRILL-3101) Setting "slice_target" to 1 changes the order of the columns in a "select *" query with order by

[ https://issues.apache.org/jira/browse/DRILL-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545973#comment-14545973 ] Jinfeng Ni commented on DRILL-3101: --- Right. That's the behavior caused by Merging oper

[jira] [Commented] (DRILL-3044) Very deep record batch fetching stack for single table query (TestTpchLimit0.tpch01)

[ https://issues.apache.org/jira/browse/DRILL-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541084#comment-14541084 ] Jinfeng Ni commented on DRILL-3044: --- Here is the verbose physical plan for tpch01 limit

[jira] [Commented] (DRILL-2953) Group By + Order By query results are not ordered.

[ https://issues.apache.org/jira/browse/DRILL-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539307#comment-14539307 ] Jinfeng Ni commented on DRILL-2953: --- I could not locate the exact cause of the problem.

[jira] [Updated] (DRILL-2929) Join query does not return results/error/exception, appears to be hung

[ https://issues.apache.org/jira/browse/DRILL-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2929: -- Fix Version/s: (was: 1.0.0) 1.1.0 > Join query does not return results/error/exce

[jira] [Assigned] (DRILL-2929) Join query does not return results/error/exception, appears to be hung

[ https://issues.apache.org/jira/browse/DRILL-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni reassigned DRILL-2929: - Assignee: Jinfeng Ni (was: Sean Hsuan-Yi Chu) > Join query does not return results/error/excepti

[jira] [Commented] (DRILL-2953) Group By + Order By query results are not ordered.

[ https://issues.apache.org/jira/browse/DRILL-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538988#comment-14538988 ] Jinfeng Ni commented on DRILL-2953: --- One more case: {code} select cast(columns[0] as in

[jira] [Commented] (DRILL-2953) Group By + Order By query results are not ordered.

[ https://issues.apache.org/jira/browse/DRILL-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538939#comment-14538939 ] Jinfeng Ni commented on DRILL-2953: --- Skipping the middle CAST(b) means the output of pro

[jira] [Commented] (DRILL-3028) Exception in correlated subquery with exists when columns in subquery are not qualified

[ https://issues.apache.org/jira/browse/DRILL-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538895#comment-14538895 ] Jinfeng Ni commented on DRILL-3028: --- The query with qualification is actually different

[jira] [Commented] (DRILL-2953) Group By + Order By query results are not ordered.

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

[jira] [Updated] (DRILL-2953) Group By + Order By query results are not ordered.

[ https://issues.apache.org/jira/browse/DRILL-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2953: -- Attachment: 0001-DRILL-2953-Ensure-sort-would-be-enforced-when-a-cast.patch > Group By + Order By query

[jira] [Commented] (DRILL-3018) Queries with scalar aggregate and non equality (non correlated) fail to plan

[ https://issues.apache.org/jira/browse/DRILL-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538632#comment-14538632 ] Jinfeng Ni commented on DRILL-3018: --- Fixed in commit a7359f36b517e667b7e64a474154fb5b223

[jira] [Commented] (DRILL-3018) Queries with scalar aggregate and non equality (non correlated) fail to plan

[ https://issues.apache.org/jira/browse/DRILL-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538596#comment-14538596 ] Jinfeng Ni commented on DRILL-3018: --- Agree. Will try to push the change back to Calcite

[jira] [Commented] (DRILL-3018) Queries with scalar aggregate and non equality (non correlated) fail to plan

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

[jira] [Updated] (DRILL-3018) Queries with scalar aggregate and non equality (non correlated) fail to plan

[ https://issues.apache.org/jira/browse/DRILL-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-3018: -- Attachment: 0001-DRILL-3018-Fix-CanNotPlan-for-nestLoop-left-join-cau.patch > Queries with scalar aggreg

[jira] [Comment Edited] (DRILL-3018) Queries with scalar aggregate and non equality (non correlated) fail to plan

[ https://issues.apache.org/jira/browse/DRILL-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537567#comment-14537567 ] Jinfeng Ni edited comment on DRILL-3018 at 5/11/15 5:01 AM: He

[jira] [Commented] (DRILL-3018) Queries with scalar aggregate and non equality (non correlated) fail to plan

[ https://issues.apache.org/jira/browse/DRILL-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537567#comment-14537567 ] Jinfeng Ni commented on DRILL-3018: --- Here is the reason for CanNotPlan for this query, a

[jira] [Commented] (DRILL-3009) Reduce the IN list threshold to 10 to take advantage of Values operator

[ https://issues.apache.org/jira/browse/DRILL-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537002#comment-14537002 ] Jinfeng Ni commented on DRILL-3009: --- +1 > Reduce the IN list threshold to 10 to take ad

[jira] [Commented] (DRILL-2958) Move Drill to alternative cost-based planner for Join planning

[ https://issues.apache.org/jira/browse/DRILL-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536032#comment-14536032 ] Jinfeng Ni commented on DRILL-2958: --- Copy from review board about a summary of change in

[jira] [Commented] (DRILL-2958) Move Drill to alternative cost-based planner for Join planning

[ https://issues.apache.org/jira/browse/DRILL-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536031#comment-14536031 ] Jinfeng Ni commented on DRILL-2958: --- Reviewboard link: https://reviews.apache.org/r/340

[jira] [Updated] (DRILL-2962) Correlates subquery with scalar aggregate or scalar aggregate with expression throws and error

[ https://issues.apache.org/jira/browse/DRILL-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2962: -- Assignee: Aman Sinha (was: Jinfeng Ni) > Correlates subquery with scalar aggregate or scalar aggregate

[jira] [Updated] (DRILL-2914) regression: Mondrian query534.q, drill give wrong result

[ https://issues.apache.org/jira/browse/DRILL-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2914: -- Assignee: Sean Hsuan-Yi Chu (was: Jinfeng Ni) > regression: Mondrian query534.q, drill give wrong resul

[jira] [Commented] (DRILL-2953) Group By + Order By query results are not ordered.

[ https://issues.apache.org/jira/browse/DRILL-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527544#comment-14527544 ] Jinfeng Ni commented on DRILL-2953: --- There seems to be a bug in planner. The the first

[jira] [Updated] (DRILL-2953) Group By + Order By query results are not ordered.

[ https://issues.apache.org/jira/browse/DRILL-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2953: -- Fix Version/s: 1.0.0 > Group By + Order By query results are not ordered. >

[jira] [Resolved] (DRILL-2761) ParquetGroupScan copy constructor only copy reference, leading to out-sync ParquetGroupScan instance.

[ https://issues.apache.org/jira/browse/DRILL-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-2761. --- Resolution: Fixed commit id: e462d14e63e4b396935f611cba5183c6f5d62a8f > ParquetGroupScan copy constru

[jira] [Resolved] (DRILL-1384) Rebase Drill on Calcite v1.0

[ https://issues.apache.org/jira/browse/DRILL-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-1384. --- Resolution: Fixed commit id: e99f270322ec17580e728bf28a20b978a7fbdf8b > Rebase Drill on Calcite v1

[jira] [Commented] (DRILL-1384) Rebase Drill on Calcite v1.0

[ https://issues.apache.org/jira/browse/DRILL-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509239#comment-14509239 ] Jinfeng Ni commented on DRILL-1384: --- Review board link: https://reviews.apache.org/r/33

[jira] [Commented] (DRILL-2824) Function resolution should be deterministic

[ https://issues.apache.org/jira/browse/DRILL-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507326#comment-14507326 ] Jinfeng Ni commented on DRILL-2824: --- +1. Overall looks good to me. Two comments: 1). c

[jira] [Commented] (DRILL-2753) Implicit cast fails when comparing a double column and a varchar literal

[ https://issues.apache.org/jira/browse/DRILL-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504122#comment-14504122 ] Jinfeng Ni commented on DRILL-2753: --- +1. > Implicit cast fails when comparing a double

[jira] [Commented] (DRILL-2827) Allow implicit cast from strings to boolean

[ https://issues.apache.org/jira/browse/DRILL-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502006#comment-14502006 ] Jinfeng Ni commented on DRILL-2827: --- +1. LGTM. > Allow implicit cast from strings to b

[jira] [Commented] (DRILL-2761) ParquetGroupScan copy constructor only copy reference, leading to out-sync ParquetGroupScan instance.

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

[jira] [Updated] (DRILL-2761) ParquetGroupScan copy constructor only copy reference, leading to out-sync ParquetGroupScan instance.

[ https://issues.apache.org/jira/browse/DRILL-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2761: -- Attachment: 0003-DRILL-2761-ParquetGroupScan-s-copy-constructor-shoul.patch > ParquetGroupScan copy cons

[jira] [Updated] (DRILL-1384) Rebase Drill on Calcite v1.0

[ https://issues.apache.org/jira/browse/DRILL-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-1384: -- Summary: Rebase Drill on Calcite v1.0 (was: Get off Calcite fork) > Rebase Drill on Calcite v1.0 >

[jira] [Updated] (DRILL-2794) Partition pruning is not happening correctly when maxdir/mindir is used in the filter condition

[ https://issues.apache.org/jira/browse/DRILL-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2794: -- Assignee: Jason Altekruse (was: Jinfeng Ni) > Partition pruning is not happening correctly when maxdir/

[jira] [Updated] (DRILL-2753) Implicit cast fails when comparing a double column and a double literal

[ https://issues.apache.org/jira/browse/DRILL-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2753: -- Assignee: Mehant Baid (was: Jinfeng Ni) > Implicit cast fails when comparing a double column and a doub

[jira] [Updated] (DRILL-2753) Implicit cast fails when comparing a double column and a double literal

[ https://issues.apache.org/jira/browse/DRILL-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2753: -- Component/s: (was: Query Planning & Optimization) Functions - Drill > Implicit cast

[jira] [Commented] (DRILL-2785) Aggregate MAX query on a directory fails with SQLException

[ https://issues.apache.org/jira/browse/DRILL-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494716#comment-14494716 ] Jinfeng Ni commented on DRILL-2785: --- The query plan looks fine to me. From the error msg

[jira] [Updated] (DRILL-1532) Query fails when specifying schema name with column name

[ https://issues.apache.org/jira/browse/DRILL-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-1532: -- Fix Version/s: (was: 0.9.0) 1.0.0 > Query fails when specifying schema name with

[jira] [Commented] (DRILL-2422) Querying views having the same name as their datasource fails

[ https://issues.apache.org/jira/browse/DRILL-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492671#comment-14492671 ] Jinfeng Ni commented on DRILL-2422: --- Assign to Venki, since we should block view's creat

[jira] [Updated] (DRILL-2422) Querying views having the same name as their datasource fails

[ https://issues.apache.org/jira/browse/DRILL-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2422: -- Assignee: Venki Korukanti (was: Jinfeng Ni) > Querying views having the same name as their datasource f

[jira] [Created] (DRILL-2761) ParquetGroupScan copy constructor only copy reference, leading to out-sync ParquetGroupScan instance.

Jinfeng Ni created DRILL-2761: - Summary: ParquetGroupScan copy constructor only copy reference, leading to out-sync ParquetGroupScan instance. Key: DRILL-2761 URL: https://issues.apache.org/jira/browse/DRILL-2761

[jira] [Commented] (DRILL-2714) Exchange should be removed if Drill scans a local system table

[ https://issues.apache.org/jira/browse/DRILL-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487681#comment-14487681 ] Jinfeng Ni commented on DRILL-2714: --- +1. > Exchange should be removed if Drill scans a

[jira] [Resolved] (DRILL-2714) Exchange should be removed if Drill scans a local system table

[ https://issues.apache.org/jira/browse/DRILL-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-2714. --- Resolution: Fixed Fixed in cbfe5772d02b6bb36af9ffd6c8572d612b4a88d5. > Exchange should be removed if

[jira] [Updated] (DRILL-2704) Schema change not reported in Union All query

[ https://issues.apache.org/jira/browse/DRILL-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2704: -- Assignee: Sean Hsuan-Yi Chu (was: Jinfeng Ni) > Schema change not reported in Union All query > ---

[jira] [Updated] (DRILL-2688) Use of ORDER BY on right side of Union All results in SqlValidatorException

[ https://issues.apache.org/jira/browse/DRILL-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2688: -- Assignee: Sean Hsuan-Yi Chu (was: Jinfeng Ni) > Use of ORDER BY on right side of Union All results in S

[jira] [Updated] (DRILL-1784) Ignore boolean type enforcement on filter conditions during validation

[ https://issues.apache.org/jira/browse/DRILL-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-1784: -- Assignee: Sean Hsuan-Yi Chu (was: Jinfeng Ni) > Ignore boolean type enforcement on filter conditions du

[jira] [Commented] (DRILL-2458) Extra hash column added when running CTAS with order by

[ https://issues.apache.org/jira/browse/DRILL-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389841#comment-14389841 ] Jinfeng Ni commented on DRILL-2458: --- Fixed in commit : 7b11e3e8fd5f0263e2165df413b36d48f

[jira] [Resolved] (DRILL-2633) Visitors (PreProcessLogicalRel and UnsupportedOperatorsVisitor) are shared unsafely

[ https://issues.apache.org/jira/browse/DRILL-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-2633. --- Resolution: Fixed Fix Version/s: 0.9.0 > Visitors (PreProcessLogicalRel and UnsupportedOperator

[jira] [Commented] (DRILL-2633) Visitors (PreProcessLogicalRel and UnsupportedOperatorsVisitor) are shared unsafely

[ https://issues.apache.org/jira/browse/DRILL-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389824#comment-14389824 ] Jinfeng Ni commented on DRILL-2633: --- +1. > Visitors (PreProcessLogicalRel and Unsupp

[jira] [Commented] (DRILL-2633) Visitors (PreProcessLogicalRel and UnsupportedOperatorsVisitor) are shared unsafely

[ https://issues.apache.org/jira/browse/DRILL-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389827#comment-14389827 ] Jinfeng Ni commented on DRILL-2633: --- fixed in commit : 064fc026561716f76f3548d35df602bac

[jira] [Commented] (DRILL-2422) Querying views having the same name as their datasource fails

[ https://issues.apache.org/jira/browse/DRILL-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389487#comment-14389487 ] Jinfeng Ni commented on DRILL-2422: --- If we are creating the same name (either create vie

[jira] [Commented] (DRILL-2639) Panner bug - RelOptPlanner.CannotPlanException

[ https://issues.apache.org/jira/browse/DRILL-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389431#comment-14389431 ] Jinfeng Ni commented on DRILL-2639: --- Sean, please take a look, since it's related to UNI

[jira] [Updated] (DRILL-2639) Panner bug - RelOptPlanner.CannotPlanException

[ https://issues.apache.org/jira/browse/DRILL-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2639: -- Assignee: Sean Hsuan-Yi Chu (was: Jinfeng Ni) > Panner bug - RelOptPlanner.CannotPlanException > --

[jira] [Updated] (DRILL-2631) Project one column from output of Union All results in Column count mismatch in UNION ALL

[ https://issues.apache.org/jira/browse/DRILL-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2631: -- Assignee: Sean Hsuan-Yi Chu (was: Jinfeng Ni) > Project one column from output of Union All results in

[jira] [Updated] (DRILL-2630) Merge join over inputs with complex type hit run-time code compiler error

[ https://issues.apache.org/jira/browse/DRILL-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2630: -- Attachment: complex_1.json Attach the sample JSON file used in the query. > Merge join over inputs wi

[jira] [Created] (DRILL-2630) Merge join over inputs with complex type hit run-time code compiler error

Jinfeng Ni created DRILL-2630: - Summary: Merge join over inputs with complex type hit run-time code compiler error Key: DRILL-2630 URL: https://issues.apache.org/jira/browse/DRILL-2630 Project: Apache Dri

[jira] [Updated] (DRILL-2608) Union all query fails when json.all_text_mode=false

[ https://issues.apache.org/jira/browse/DRILL-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2608: -- Assignee: Sean Hsuan-Yi Chu (was: Jinfeng Ni) > Union all query fails when json.all_text_mode=false > -

[jira] [Created] (DRILL-2579) JDBC unit tests will timeout after one testcase failed with unexpected results.

Jinfeng Ni created DRILL-2579: - Summary: JDBC unit tests will timeout after one testcase failed with unexpected results. Key: DRILL-2579 URL: https://issues.apache.org/jira/browse/DRILL-2579 Project: Ap

[jira] [Commented] (DRILL-2099) Order by has issues with repeated map within a repeated map

[ https://issues.apache.org/jira/browse/DRILL-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378261#comment-14378261 ] Jinfeng Ni commented on DRILL-2099: --- +1. LGTM. I have one question. I saw there are oth

[jira] [Commented] (DRILL-2301) Query fails when multiple table aliases are provided for CTEs

[ https://issues.apache.org/jira/browse/DRILL-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376942#comment-14376942 ] Jinfeng Ni commented on DRILL-2301: --- This seems to be same as CAICTE-603. https://issue

[jira] [Updated] (DRILL-2517) Partition pruning still reading files during planning

[ https://issues.apache.org/jira/browse/DRILL-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2517: -- Assignee: Aman Sinha (was: Jinfeng Ni) > Partition pruning still reading files during planning > --

[jira] [Updated] (DRILL-2458) Extra hash column added when running CTAS with order by

[ https://issues.apache.org/jira/browse/DRILL-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2458: -- Fix Version/s: 0.9.0 > Extra hash column added when running CTAS with order by > ---

[jira] [Updated] (DRILL-2458) Extra hash column added when running CTAS with order by

[ https://issues.apache.org/jira/browse/DRILL-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2458: -- Attachment: 0001-DRILL-2458-Ensure-no-unwanted-columns-are-added-to-C.patch > Extra hash column added wh

[jira] [Commented] (DRILL-2458) Extra hash column added when running CTAS with order by

[ https://issues.apache.org/jira/browse/DRILL-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370069#comment-14370069 ] Jinfeng Ni commented on DRILL-2458: --- The extra column added seems not to be related to t

[jira] [Updated] (DRILL-2313) Query fails when one of the operands is a DATE literal without an explicit cast

[ https://issues.apache.org/jira/browse/DRILL-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2313: -- Fix Version/s: 0.9.0 > Query fails when one of the operands is a DATE literal without an explicit > cas

[jira] [Updated] (DRILL-2345) Join between drill table and view created on the same table throws unsupported exception

[ https://issues.apache.org/jira/browse/DRILL-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2345: -- Fix Version/s: 0.9.0 > Join between drill table and view created on the same table throws > unsupported

[jira] [Updated] (DRILL-2103) Queries on views containing average on columns containing null values fail

[ https://issues.apache.org/jira/browse/DRILL-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2103: -- Assignee: Aman Sinha (was: Jinfeng Ni) > Queries on views containing average on columns containing null

[jira] [Updated] (DRILL-2422) Querying views having the same name as their datasource fails

[ https://issues.apache.org/jira/browse/DRILL-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2422: -- Fix Version/s: 0.9.0 > Querying views having the same name as their datasource fails > -

[jira] [Updated] (DRILL-2438) Query on views with Avg on integer column returns wrong result

[ https://issues.apache.org/jira/browse/DRILL-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2438: -- Fix Version/s: 0.9.0 > Query on views with Avg on integer column returns wrong result >

[jira] [Updated] (DRILL-2438) Query on views with Avg on integer column returns wrong result

[ https://issues.apache.org/jira/browse/DRILL-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2438: -- Assignee: Aman Sinha (was: Jinfeng Ni) > Query on views with Avg on integer column returns wrong result

[jira] [Updated] (DRILL-2398) IS NOT DISTINCT FROM predicate returns incorrect result when used as a join filter

[ https://issues.apache.org/jira/browse/DRILL-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2398: -- Fix Version/s: 0.9.0 > IS NOT DISTINCT FROM predicate returns incorrect result when used as a join > fi

[jira] [Updated] (DRILL-2398) IS NOT DISTINCT FROM predicate returns incorrect result when used as a join filter

[ https://issues.apache.org/jira/browse/DRILL-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni updated DRILL-2398: -- Assignee: Aman Sinha (was: Jinfeng Ni) > IS NOT DISTINCT FROM predicate returns incorrect result when u

<    3   4   5   6   7   8   9   10   >