[jira] [Created] (DRILL-5079) PreparedStatement dynamic parameters to avoid SQL Injection test

Wahyu Sudrajat created DRILL-5079: - Summary: PreparedStatement dynamic parameters to avoid SQL Injection test Key: DRILL-5079 URL: https://issues.apache.org/jira/browse/DRILL-5079 Project: Apache

[jira] [Updated] (DRILL-5070) Code gen: create methods in fixed order to allow test verification

[ https://issues.apache.org/jira/browse/DRILL-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5070: --- Summary: Code gen: create methods in fixed order to allow test verification (was: Code cache

[jira] [Updated] (DRILL-5070) Code gen: create methods in fixed order to allow test verification

[ https://issues.apache.org/jira/browse/DRILL-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5070: --- Description: A handy technique in testing is to compare generated code against a "golden" copy that

[jira] [Issue Comment Deleted] (DRILL-5070) Code gen: create methods in fixed order to allow test verification

[ https://issues.apache.org/jira/browse/DRILL-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5070: --- Comment: was deleted (was: Analysis of impact. Method order is random. If a generated class has n

[jira] [Assigned] (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 ] Zelaine Fong reassigned DRILL-5044: --- Assignee: Paul Rogers (was: Arina Ielchiieva) Assigning to [~Paul.Rogers] for code review.

[jira] [Updated] (DRILL-5020) ExternalSortBatch has inconsistent notions of the memory limit

[ https://issues.apache.org/jira/browse/DRILL-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5020: --- Issue Type: Sub-task (was: Bug) Parent: DRILL-5080 > ExternalSortBatch has inconsistent

[jira] [Updated] (DRILL-5025) ExternalSortBatch provides weak control over spill file size

[ https://issues.apache.org/jira/browse/DRILL-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5025: --- Issue Type: Sub-task (was: Improvement) Parent: DRILL-5080 > ExternalSortBatch provides weak

[jira] [Commented] (DRILL-5077) Memory Leak -

[ https://issues.apache.org/jira/browse/DRILL-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702863#comment-15702863 ] Khurram Faraaz commented on DRILL-5077: --- To repro the problem. Run the below query {noformat}

[jira] [Updated] (DRILL-5077) Memory Leak - when foreman Drillbit is stopped

[ https://issues.apache.org/jira/browse/DRILL-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Khurram Faraaz updated DRILL-5077: -- Summary: Memory Leak - when foreman Drillbit is stopped (was: Memory Leak - ) > Memory Leak -

[jira] [Commented] (DRILL-5077) Memory Leak -

[ https://issues.apache.org/jira/browse/DRILL-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703004#comment-15703004 ] Khurram Faraaz commented on DRILL-5077: --- Problem (memory leak) is seen even when there are two

[jira] [Created] (DRILL-5080) Create a memory-managed version of the External Sort operator

Paul Rogers created DRILL-5080: -- Summary: Create a memory-managed version of the External Sort operator Key: DRILL-5080 URL: https://issues.apache.org/jira/browse/DRILL-5080 Project: Apache Drill

[jira] [Updated] (DRILL-5011) External Sort Batch memory use depends on record width

[ https://issues.apache.org/jira/browse/DRILL-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5011: --- Issue Type: Sub-task (was: Bug) Parent: DRILL-5080 > External Sort Batch memory use depends

[jira] [Updated] (DRILL-5017) Config param drill.exec.sort.external.batch.size is not used

[ https://issues.apache.org/jira/browse/DRILL-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5017: --- Issue Type: Sub-task (was: Bug) Parent: DRILL-5080 > Config param

[jira] [Updated] (DRILL-5026) ExternalSortBatch uses two memory allocators; one will do

[ https://issues.apache.org/jira/browse/DRILL-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5026: --- Issue Type: Sub-task (was: Improvement) Parent: DRILL-5080 > ExternalSortBatch uses two

[jira] [Commented] (DRILL-5058) External sort does not handle its own UserExceptions

[ https://issues.apache.org/jira/browse/DRILL-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702716#comment-15702716 ] ASF GitHub Bot commented on DRILL-5058: --- Github user paul-rogers closed the pull request at:

[jira] [Updated] (DRILL-5066) External sort attempts to retry sv2 memory alloc, even if can never succeed

[ https://issues.apache.org/jira/browse/DRILL-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5066: --- Issue Type: Sub-task (was: Bug) Parent: DRILL-5080 > External sort attempts to retry sv2

[jira] [Updated] (DRILL-5062) External sort refers to the deprecated HDFS fs.default.name param

[ https://issues.apache.org/jira/browse/DRILL-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5062: --- Issue Type: Sub-task (was: Bug) Parent: DRILL-5080 > External sort refers to the deprecated

[jira] [Updated] (DRILL-5055) External Sort does not delete spill file if error occurs during close

[ https://issues.apache.org/jira/browse/DRILL-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5055: --- Issue Type: Sub-task (was: Bug) Parent: DRILL-5080 > External Sort does not delete spill

[jira] [Commented] (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:comment-tabpanel=15702750#comment-15702750 ] ASF GitHub Bot commented on DRILL-5044: --- Github user paul-rogers commented on a diff in the pull

[jira] [Commented] (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:comment-tabpanel=15702753#comment-15702753 ] ASF GitHub Bot commented on DRILL-5044: --- Github user paul-rogers commented on a diff in the pull

[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 ] Paul Rogers updated DRILL-5044: --- Assignee: Arina Ielchiieva (was: Paul Rogers) > After the dynamic registration of multiple jars

[jira] [Updated] (DRILL-5079) PreparedStatement dynamic parameters to avoid SQL Injection test

[ https://issues.apache.org/jira/browse/DRILL-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudheesh Katkam updated DRILL-5079: --- Labels: security (was: ) > PreparedStatement dynamic parameters to avoid SQL Injection test

[jira] [Updated] (DRILL-5014) ExternalSortBatch cache size, spill count differs from config setting

[ https://issues.apache.org/jira/browse/DRILL-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5014: --- Issue Type: Sub-task (was: Bug) Parent: DRILL-5080 > ExternalSortBatch cache size, spill

[jira] [Updated] (DRILL-5008) Refactor, document and simplify ExternalSortBatch

[ https://issues.apache.org/jira/browse/DRILL-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5008: --- Issue Type: Sub-task (was: Improvement) Parent: DRILL-5080 > Refactor, document and simplify

[jira] [Commented] (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:comment-tabpanel=15702754#comment-15702754 ] ASF GitHub Bot commented on DRILL-5044: --- Github user paul-rogers commented on a diff in the pull

[jira] [Updated] (DRILL-5023) ExternalSortBatch does not spill fully, throws off spill calculations

[ https://issues.apache.org/jira/browse/DRILL-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5023: --- Issue Type: Sub-task (was: Bug) Parent: DRILL-5080 > ExternalSortBatch does not spill fully,

[jira] [Updated] (DRILL-5022) ExternalSortBatch sets two different limits for "copier" memory

[ https://issues.apache.org/jira/browse/DRILL-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5022: --- Issue Type: Sub-task (was: Bug) Parent: DRILL-5080 > ExternalSortBatch sets two different

[jira] [Updated] (DRILL-5027) ExternalSortBatch is inefficient: rewrites data unnecessarily

[ https://issues.apache.org/jira/browse/DRILL-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5027: --- Issue Type: Sub-task (was: Bug) Parent: DRILL-5080 > ExternalSortBatch is inefficient:

[jira] [Commented] (DRILL-5050) C++ client library has symbol resolution issues when loaded by a process that already uses boost::asio

[ https://issues.apache.org/jira/browse/DRILL-5050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702649#comment-15702649 ] ASF GitHub Bot commented on DRILL-5050: --- Github user laurentgo commented on the issue:

[jira] [Updated] (DRILL-5080) Create a memory-managed version of the External Sort operator

[ https://issues.apache.org/jira/browse/DRILL-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5080: --- Attachment: ManagedExternalSortDesign.pdf Design document for the managed external sort operator.

[jira] [Updated] (DRILL-5019) ExternalSortBatch spills all batches to disk even if even one spills

[ https://issues.apache.org/jira/browse/DRILL-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5019: --- Issue Type: Sub-task (was: Improvement) Parent: DRILL-5080 > ExternalSortBatch spills all

[jira] [Comment Edited] (DRILL-5077) Memory Leak -

[ https://issues.apache.org/jira/browse/DRILL-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702863#comment-15702863 ] Khurram Faraaz edited comment on DRILL-5077 at 11/28/16 7:29 PM: - To repro

[jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one

[ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703382#comment-15703382 ] ASF GitHub Bot commented on DRILL-5015: --- Github user sudheeshkatkam commented on a diff in the pull

[jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one

[ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703387#comment-15703387 ] ASF GitHub Bot commented on DRILL-5015: --- Github user sudheeshkatkam commented on a diff in the pull

[jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one

[ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703385#comment-15703385 ] ASF GitHub Bot commented on DRILL-5015: --- Github user sudheeshkatkam commented on a diff in the pull

[jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one

[ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703383#comment-15703383 ] ASF GitHub Bot commented on DRILL-5015: --- Github user sudheeshkatkam commented on a diff in the pull

[jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one

[ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703388#comment-15703388 ] ASF GitHub Bot commented on DRILL-5015: --- Github user sudheeshkatkam commented on a diff in the pull

[jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one

[ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703386#comment-15703386 ] ASF GitHub Bot commented on DRILL-5015: --- Github user sudheeshkatkam commented on a diff in the pull

[jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one

[ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703384#comment-15703384 ] ASF GitHub Bot commented on DRILL-5015: --- Github user sudheeshkatkam commented on a diff in the pull

[jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one

[ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703389#comment-15703389 ] ASF GitHub Bot commented on DRILL-5015: --- Github user sudheeshkatkam commented on a diff in the pull

[jira] [Commented] (DRILL-4347) Planning time for query64 from TPCDS test suite has increased 10 times compared to 1.4 release

[ https://issues.apache.org/jira/browse/DRILL-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703505#comment-15703505 ] Aman Sinha commented on DRILL-4347: --- Attached the full jstack output for this issue based on the latest

[jira] [Commented] (DRILL-5065) Optimize count( *) queries on MapR-DB JSON Tables

[ https://issues.apache.org/jira/browse/DRILL-5065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703289#comment-15703289 ] ASF GitHub Bot commented on DRILL-5065: --- GitHub user spanchamiamapr opened a pull request:

[jira] [Assigned] (DRILL-4347) Planning time for query64 from TPCDS test suite has increased 10 times compared to 1.4 release

[ https://issues.apache.org/jira/browse/DRILL-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Sinha reassigned DRILL-4347: - Assignee: Aman Sinha (was: Jinfeng Ni) > Planning time for query64 from TPCDS test suite has

[jira] [Updated] (DRILL-4347) Planning time for query64 from TPCDS test suite has increased 10 times compared to 1.4 release

[ https://issues.apache.org/jira/browse/DRILL-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Sinha updated DRILL-4347: -- Attachment: drill4347_jstack.txt > Planning time for query64 from TPCDS test suite has increased 10

[jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one

[ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703359#comment-15703359 ] ASF GitHub Bot commented on DRILL-5015: --- Github user parthchandra commented on the issue:

[jira] [Commented] (DRILL-5082) Metadata Cache is being refreshed every single time

[ https://issues.apache.org/jira/browse/DRILL-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703725#comment-15703725 ] Abhishek Girish commented on DRILL-5082: Did you mean fix for DRILL-4831? > Metadata Cache is

[jira] [Comment Edited] (DRILL-5083) IteratorValidator does not handle RecordIterator cleanup call to next( )

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703762#comment-15703762 ] Paul Rogers edited comment on DRILL-5083 at 11/29/16 1:13 AM: -- Stepping

[jira] [Closed] (DRILL-5078) use Custom Functions errors

[ https://issues.apache.org/jira/browse/DRILL-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mircoteam closed DRILL-5078. Resolution: Fixed thank you ,i fix all package path,it`s works now. > use Custom Functions errors >

[jira] [Commented] (DRILL-5083) IteratorValidator does not handle RecordIterator cleanup call to next( )

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703787#comment-15703787 ] Paul Rogers commented on DRILL-5083: We saw a similar issue in a production system that went into an

[jira] [Created] (DRILL-5083) IteratorValidator does not handle RecordIterator cleanup call to next( )

Paul Rogers created DRILL-5083: -- Summary: IteratorValidator does not handle RecordIterator cleanup call to next( ) Key: DRILL-5083 URL: https://issues.apache.org/jira/browse/DRILL-5083 Project: Apache

[jira] [Commented] (DRILL-5083) IteratorValidator does not handle RecordIterator cleanup call to next( )

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703762#comment-15703762 ] Paul Rogers commented on DRILL-5083: Stepping further, once the original {{MergeJoinBatch.close( )}}

[jira] [Created] (DRILL-5081) Excessive info level logging introduced in DRILL-4203

Sudheesh Katkam created DRILL-5081: -- Summary: Excessive info level logging introduced in DRILL-4203 Key: DRILL-5081 URL: https://issues.apache.org/jira/browse/DRILL-5081 Project: Apache Drill

[jira] [Updated] (DRILL-5082) Metadata Cache is being refreshed every single time

[ https://issues.apache.org/jira/browse/DRILL-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zelaine Fong updated DRILL-5082: Assignee: Padma Penumarthy > Metadata Cache is being refreshed every single time >

[jira] [Comment Edited] (DRILL-5083) IteratorValidator does not handle RecordIterator cleanup call to next( )

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15704033#comment-15704033 ] Paul Rogers edited comment on DRILL-5083 at 11/29/16 3:25 AM: -- More info. The

[jira] [Created] (DRILL-5084) How read CVS file supports GBK encoding

mircoteam created DRILL-5084: Summary: How read CVS file supports GBK encoding Key: DRILL-5084 URL: https://issues.apache.org/jira/browse/DRILL-5084 Project: Apache Drill Issue Type: Wish

[jira] [Commented] (DRILL-5083) IteratorValidator does not handle RecordIterator cleanup call to next( )

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703972#comment-15703972 ] Paul Rogers commented on DRILL-5083: Looking at {{AbstractRecordBatch.next( )}}: If the operator ended

[jira] [Commented] (DRILL-5083) IteratorValidator does not handle RecordIterator cleanup call to next( )

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15704007#comment-15704007 ] Paul Rogers commented on DRILL-5083: The looping call stack shown earlier calls from the

[jira] [Commented] (DRILL-5083) IteratorValidator does not handle RecordIterator cleanup call to next( )

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15704033#comment-15704033 ] Paul Rogers commented on DRILL-5083: More info. The query in question had, in essence: {code} - Merge

[jira] [Commented] (DRILL-5083) IteratorValidator does not handle RecordIterator cleanup call to next( )

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15704314#comment-15704314 ] Paul Rogers commented on DRILL-5083: It seems that only the {{RecordIterator}} has the

[jira] [Comment Edited] (DRILL-5083) IteratorValidator does not handle RecordIterator cleanup call to next( )

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15704033#comment-15704033 ] Paul Rogers edited comment on DRILL-5083 at 11/29/16 4:54 AM: -- More info. The

[jira] [Comment Edited] (DRILL-5083) IteratorValidator does not handle RecordIterator cleanup call to next( )

[ https://issues.apache.org/jira/browse/DRILL-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15704033#comment-15704033 ] Paul Rogers edited comment on DRILL-5083 at 11/29/16 5:42 AM: -- More info. The

[jira] [Updated] (DRILL-5084) How read CSV file supports GBK encoding

[ https://issues.apache.org/jira/browse/DRILL-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mircoteam updated DRILL-5084: - Summary: How read CSV file supports GBK encoding (was: How read CVS file supports GBK encoding) > How

[jira] [Commented] (DRILL-5084) How read CSV file supports GBK encoding

[ https://issues.apache.org/jira/browse/DRILL-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15704535#comment-15704535 ] mircoteam commented on DRILL-5084: -- Oh sorry, I think this`s about csv encoding. i change csv encoding to

[jira] [Closed] (DRILL-5084) How read CSV file supports GBK encoding

[ https://issues.apache.org/jira/browse/DRILL-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mircoteam closed DRILL-5084. Resolution: Fixed change csv encoding to UTF-8 > How read CSV file supports GBK encoding >

[jira] [Created] (DRILL-5078) use Custom Functions errors

mircoteam created DRILL-5078: Summary: use Custom Functions errors Key: DRILL-5078 URL: https://issues.apache.org/jira/browse/DRILL-5078 Project: Apache Drill Issue Type: Bug

[jira] [Commented] (DRILL-5078) use Custom Functions errors

[ https://issues.apache.org/jira/browse/DRILL-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15701635#comment-15701635 ] Arina Ielchiieva commented on DRILL-5078: - Did you try to use class fully qualified name

[jira] [Commented] (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:comment-tabpanel=15701673#comment-15701673 ] Arina Ielchiieva commented on DRILL-5044: - The reason of this failure is that when update to

[jira] [Commented] (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:comment-tabpanel=15701703#comment-15701703 ] ASF GitHub Bot commented on DRILL-5044: --- GitHub user arina-ielchiieva opened a pull request: