[jira] [Commented] (DRILL-3993) Rebase Drill on Calcite master branch

[ https://issues.apache.org/jira/browse/DRILL-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149069#comment-16149069 ] Roman commented on DRILL-3993: -- I am working on updating Drill Calcite version to 1.13. I forked from Calcite

[jira] [Resolved] (DRILL-3119) Query stays in "CANCELLATION_REQUESTED" status in UI after OOM of Direct buffer memory

[ https://issues.apache.org/jira/browse/DRILL-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman resolved DRILL-3119. -- Resolution: Duplicate Fix Version/s: 1.11.0 > Query stays in "CANCELLATION_REQUESTED" status in UI after

[jira] [Commented] (DRILL-3119) Query stays in "CANCELLATION_REQUESTED" status in UI after OOM of Direct buffer memory

[ https://issues.apache.org/jira/browse/DRILL-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114634#comment-16114634 ] Roman commented on DRILL-3119: -- I tried to reproduce this issue on 1 drillbit cluster using

[jira] [Assigned] (DRILL-3119) Query stays in "CANCELLATION_REQUESTED" status in UI after OOM of Direct buffer memory

[ https://issues.apache.org/jira/browse/DRILL-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman reassigned DRILL-3119: Assignee: Roman > Query stays in "CANCELLATION_REQUESTED" status in UI after OOM of Direct > buffer

[jira] [Resolved] (DRILL-3665) Deadlock while executing CTAS that runs out of memory

[ https://issues.apache.org/jira/browse/DRILL-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman resolved DRILL-3665. -- Resolution: Duplicate Fix Version/s: (was: Future) 1.11.0 > Deadlock while

[jira] [Commented] (DRILL-3665) Deadlock while executing CTAS that runs out of memory

[ https://issues.apache.org/jira/browse/DRILL-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113185#comment-16113185 ] Roman commented on DRILL-3665: -- I tried different ways to reproduce this issue on a drill a7e298760f9c9e

[jira] [Assigned] (DRILL-3665) Deadlock while executing CTAS that runs out of memory

[ https://issues.apache.org/jira/browse/DRILL-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman reassigned DRILL-3665: Assignee: Roman (was: Deneche A. Hakim) > Deadlock while executing CTAS that runs out of memory >

[jira] [Commented] (DRILL-4685) RpcException: Data not accepted downstream

[ https://issues.apache.org/jira/browse/DRILL-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102035#comment-16102035 ] Roman commented on DRILL-4685: -- I tried to reproduce this issue on 1 drillbit cluster with Drill from master

[jira] [Resolved] (DRILL-4685) RpcException: Data not accepted downstream

[ https://issues.apache.org/jira/browse/DRILL-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman resolved DRILL-4685. -- Resolution: Cannot Reproduce > RpcException: Data not accepted downstream >

[jira] [Assigned] (DRILL-4685) RpcException: Data not accepted downstream

[ https://issues.apache.org/jira/browse/DRILL-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman reassigned DRILL-4685: Assignee: Roman > RpcException: Data not accepted downstream > --

[jira] [Commented] (DRILL-5083) RecordIterator can sometimes restart a query on close

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16093486#comment-16093486 ] Roman commented on DRILL-5083: -- [~paul-rogers], During the investigation, I added more logs in Drill and I

[jira] [Comment Edited] (DRILL-5083) RecordIterator can sometimes restart a query on close

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16093471#comment-16093471 ] Roman edited comment on DRILL-5083 at 7/19/17 5:42 PM: --- It seems I got some

[jira] [Comment Edited] (DRILL-5083) RecordIterator can sometimes restart a query on close

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16093471#comment-16093471 ] Roman edited comment on DRILL-5083 at 7/19/17 5:39 PM: --- It seems I got some

[jira] [Commented] (DRILL-5083) RecordIterator can sometimes restart a query on close

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16093471#comment-16093471 ] Roman commented on DRILL-5083: -- It seems I got some reproduce of this issue. I use Drill from master

[jira] [Commented] (DRILL-5239) Drill text reader reports wrong results when column value starts with '#'

[ https://issues.apache.org/jira/browse/DRILL-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075143#comment-16075143 ] Roman commented on DRILL-5239: -- [~paul-rogers], Thank you for the great introduction at CSV files at all! So

[jira] [Commented] (DRILL-5239) Drill text reader reports wrong results when column value starts with '#'

[ https://issues.apache.org/jira/browse/DRILL-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073940#comment-16073940 ] Roman commented on DRILL-5239: -- [~paul-rogers], I want to add 2 system/session options: - 1st option should

[jira] [Closed] (DRILL-5609) Resources leak on parquet table when the query hangs with CANCELLATION_REQUESTED state

[ https://issues.apache.org/jira/browse/DRILL-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman closed DRILL-5609. Resolution: Duplicate > Resources leak on parquet table when the query hangs with > CANCELLATION_REQUESTED state >

[jira] [Commented] (DRILL-5609) Resources leak on parquet table when the query hangs with CANCELLATION_REQUESTED state

[ https://issues.apache.org/jira/browse/DRILL-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072243#comment-16072243 ] Roman commented on DRILL-5609: -- This issue is duplicated with DRILL-5420. Can not reproduce it with

[jira] [Commented] (DRILL-4310) Memory leak in hash partition sender when query is cancelled

[ https://issues.apache.org/jira/browse/DRILL-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063153#comment-16063153 ] Roman commented on DRILL-4310: -- Can't reproduce this issue on local cluster. [~vicky] could you please check

[jira] [Commented] (DRILL-4595) FragmentExecutor.fail() should interrupt the fragment thread to avoid possible query hangs

[ https://issues.apache.org/jira/browse/DRILL-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063113#comment-16063113 ] Roman commented on DRILL-4595: -- I tried steps from previous comment on Drill after DRILL-5599 fix and it

[jira] [Commented] (DRILL-4595) FragmentExecutor.fail() should interrupt the fragment thread to avoid possible query hangs

[ https://issues.apache.org/jira/browse/DRILL-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063080#comment-16063080 ] Roman commented on DRILL-4595: -- I tried to catch some issues with CTAS queries and got something. Steps: 1)

[jira] [Updated] (DRILL-5609) Resources leak on parquet table when the query hangs with CANCELLATION_REQUESTED state

[ https://issues.apache.org/jira/browse/DRILL-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman updated DRILL-5609: - Attachment: Cancellation_requested_parquet_1.jpg Cancellation_requested_parquet_2.jpg

[jira] [Created] (DRILL-5609) Resources leak on parquet table when the query hangs with CANCELLATION_REQUESTED state

Roman created DRILL-5609: Summary: Resources leak on parquet table when the query hangs with CANCELLATION_REQUESTED state Key: DRILL-5609 URL: https://issues.apache.org/jira/browse/DRILL-5609 Project: Apache

[jira] [Commented] (DRILL-3091) Cancelled query continues to list on Drill UI with CANCELLATION_REQUESTED state

[ https://issues.apache.org/jira/browse/DRILL-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060816#comment-16060816 ] Roman commented on DRILL-3091: -- Can't reproduce it with TPC-DS SF 100 - query 2. I also tried to change

[jira] [Closed] (DRILL-4963) Issues when overloading Drill native functions with dynamic UDFs

[ https://issues.apache.org/jira/browse/DRILL-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman closed DRILL-4963. I have tested this issue and it was not reproduced. Verified and closed. > Issues when overloading Drill native

[jira] [Comment Edited] (DRILL-4963) Issues when overloading Drill native functions with dynamic UDFs

[ https://issues.apache.org/jira/browse/DRILL-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766723#comment-15766723 ] Roman edited comment on DRILL-4963 at 12/21/16 10:42 AM: - Added jars

[jira] [Updated] (DRILL-4963) Issues when overloading Drill native functions with dynamic UDFs

[ https://issues.apache.org/jira/browse/DRILL-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman updated DRILL-4963: - Attachment: subquery_udf-1.0-sources.jar subquery_udf-1.0.jar Added jars > Issues when

[jira] [Commented] (DRILL-4963) Issues when overloading Drill native functions with dynamic UDFs

[ https://issues.apache.org/jira/browse/DRILL-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766721#comment-15766721 ] Roman commented on DRILL-4963: -- Found similar case with different error: Run query for first time:

[jira] [Closed] (DRILL-5044) Fix retry logic to handle VersionMismatchException by not deleting jars in remote UDFs area

[ https://issues.apache.org/jira/browse/DRILL-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman closed DRILL-5044. Tested on 2-nodes cluster. Verified and closed. > Fix retry logic to handle VersionMismatchException by not deleting

[jira] [Closed] (DRILL-5007) Dynamic UDF lazy-init does not work correctly in multi-node cluster

[ https://issues.apache.org/jira/browse/DRILL-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman closed DRILL-5007. Tested on 2-nodes cluster. Verified and closed. > Dynamic UDF lazy-init does not work correctly in multi-node cluster

[jira] [Commented] (DRILL-4995) Allow lazy init when dynamic UDF support is disabled

[ https://issues.apache.org/jira/browse/DRILL-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732362#comment-15732362 ] Roman commented on DRILL-4995: -- I have tested this issue on 2-nodes cluster and it was not reproduced.

[jira] [Closed] (DRILL-4995) Allow lazy init when dynamic UDF support is disabled

[ https://issues.apache.org/jira/browse/DRILL-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman closed DRILL-4995. > Allow lazy init when dynamic UDF support is disabled > > >

[jira] [Updated] (DRILL-5044) After the dynamic registration of multiple jars simultaneously not all UDFs were registered

[ https://issues.apache.org/jira/browse/DRILL-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman updated DRILL-5044: - Description: I tried to register 21 jars simultaneously (property 'udf.retry-attempts' = 30) and not all jars

[jira] [Created] (DRILL-5044) After the dynamic registration of multiple jars simultaneously not all UDFs were registered

Roman created DRILL-5044: Summary: After the dynamic registration of multiple jars simultaneously not all UDFs were registered Key: DRILL-5044 URL: https://issues.apache.org/jira/browse/DRILL-5044 Project:

[jira] [Commented] (DRILL-5007) Dynamic UDF lazy-init does not work correctly in multi-node cluster

[ https://issues.apache.org/jira/browse/DRILL-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15648068#comment-15648068 ] Roman commented on DRILL-5007: -- Added log: org.apache.drill.exec.exception.SchemaChangeException: Failure

[jira] [Updated] (DRILL-4963) Issues when overloading Drill native functions with dynamic UDFs

[ https://issues.apache.org/jira/browse/DRILL-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman updated DRILL-4963: - Attachment: test_overloading-1.0-sources.jar test_overloading-1.0.jar Added testing jars. >

[jira] [Updated] (DRILL-5007) Dynamic UDF lazy-init does not work correctly in multi-node cluster

[ https://issues.apache.org/jira/browse/DRILL-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman updated DRILL-5007: - Description: Reproduced in .csv file with 25 different fields, 2712474 lines and 570 MB amount of data. When I

[jira] [Created] (DRILL-5007) Dynamic UDF lazy-init does not work correctly in multi-node cluster

Roman created DRILL-5007: Summary: Dynamic UDF lazy-init does not work correctly in multi-node cluster Key: DRILL-5007 URL: https://issues.apache.org/jira/browse/DRILL-5007 Project: Apache Drill

[jira] [Created] (DRILL-4995) Allow lazy init when dynamic UDF support is disabled

Roman created DRILL-4995: Summary: Allow lazy init when dynamic UDF support is disabled Key: DRILL-4995 URL: https://issues.apache.org/jira/browse/DRILL-4995 Project: Apache Drill Issue Type: Bug

[jira] [Created] (DRILL-4963) Issues when overloading Drill native functions with dynamic UDFs

Roman created DRILL-4963: Summary: Issues when overloading Drill native functions with dynamic UDFs Key: DRILL-4963 URL: https://issues.apache.org/jira/browse/DRILL-4963 Project: Apache Drill Issue

[jira] [Created] (DRILL-4962) Drill registers UDFs from packages which were not included in drill-module.conf

Roman created DRILL-4962: Summary: Drill registers UDFs from packages which were not included in drill-module.conf Key: DRILL-4962 URL: https://issues.apache.org/jira/browse/DRILL-4962 Project: Apache Drill

[jira] [Commented] (DRILL-4927) Add support for Null Equality Joins

[ https://issues.apache.org/jira/browse/DRILL-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15571628#comment-15571628 ] Roman commented on DRILL-4927: -- Merged into apache master with commit a29f1e292fc80. > Add support for Null

[jira] [Updated] (DRILL-4927) Add support for Null Equality Joins

[ https://issues.apache.org/jira/browse/DRILL-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman updated DRILL-4927: - Description: Join with an equality condition which allows null=null fails. For example, if we use some of this

[jira] [Created] (DRILL-4926) Add support for Null Equality Joins

Roman created DRILL-4926: Summary: Add support for Null Equality Joins Key: DRILL-4926 URL: https://issues.apache.org/jira/browse/DRILL-4926 Project: Apache Drill Issue Type: Improvement

[jira] [Created] (DRILL-4927) Add support for Null Equality Joins

Roman created DRILL-4927: Summary: Add support for Null Equality Joins Key: DRILL-4927 URL: https://issues.apache.org/jira/browse/DRILL-4927 Project: Apache Drill Issue Type: Improvement

[jira] [Commented] (DRILL-4824) JSON with complex nested data produces incorrect output with missing fields

[ https://issues.apache.org/jira/browse/DRILL-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466969#comment-15466969 ] Roman commented on DRILL-4824: -- I want to note, in case of this "example.json" file:

[jira] [Commented] (DRILL-4824) JSON with complex nested data produces incorrect output with missing fields

[ https://issues.apache.org/jira/browse/DRILL-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466947#comment-15466947 ] Roman commented on DRILL-4824: -- I want to note, in case of this "example.json" file: > JSON with complex

[jira] [Issue Comment Deleted] (DRILL-4824) JSON with complex nested data produces incorrect output with missing fields

[ https://issues.apache.org/jira/browse/DRILL-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman updated DRILL-4824: - Comment: was deleted (was: I want to note, in case of this "example.json" file:) > JSON with complex nested data

[jira] [Assigned] (DRILL-3562) Query fails when using flatten on JSON data where some documents have an empty array

[ https://issues.apache.org/jira/browse/DRILL-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman reassigned DRILL-3562: Assignee: Roman > Query fails when using flatten on JSON data where some documents have an > empty array

[jira] [Updated] (DRILL-4824) JSON with complex nested data produces incorrect output with missing fields

[ https://issues.apache.org/jira/browse/DRILL-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman updated DRILL-4824: - Affects Version/s: (was: 1.7.0) 1.0.0 > JSON with complex nested data produces

[jira] [Updated] (DRILL-4824) JSON with complex nested data produces incorrect output with missing fields

[ https://issues.apache.org/jira/browse/DRILL-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman updated DRILL-4824: - Description: There is incorrect output in case of JSON file with complex nested data. Here is a JSON file:

[jira] [Created] (DRILL-4824) JSON with complex nested data produces incorrect output with missing fields

Roman created DRILL-4824: Summary: JSON with complex nested data produces incorrect output with missing fields Key: DRILL-4824 URL: https://issues.apache.org/jira/browse/DRILL-4824 Project: Apache Drill