[jira] [Commented] (DRILL-8158) Remove non-reproducible build outputs
[ https://issues.apache.org/jira/browse/DRILL-8158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566159#comment-17566159 ] ASF GitHub Bot commented on DRILL-8158: --- jnturton merged PR #2590: URL: https://github.com/apache/drill/pull/2590 > Remove non-reproducible build outputs > - > > Key: DRILL-8158 > URL: https://issues.apache.org/jira/browse/DRILL-8158 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.20.0 >Reporter: Herve Boutemy >Assignee: James Turton >Priority: Major > Fix For: 1.20.2 > > > For context see [1] and [2]. The git-commit-id plugin includes information > like build host, email and time which is not compatible with a reproducible > build. Drill's built in sys.version table will return the build email and > time if they are present in the build's git.properties file so these columns > must be deprecated. Other useful Git-related information is retained. > In accompanying commits, some Kerberos unit test fixes are applied, and the > tests reenabled, and some updates to Release.md are included. > [1] [https://maven.apache.org/guides/mini/guide-reproducible-builds.html] > [2] > [https://github.com/jvm-repo-rebuild/reproducible-central#org.apache.drill:drill-root] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DRILL-8158) Remove non-reproducible build outputs
[ https://issues.apache.org/jira/browse/DRILL-8158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566158#comment-17566158 ] ASF GitHub Bot commented on DRILL-8158: --- jnturton commented on code in PR #2590: URL: https://github.com/apache/drill/pull/2590#discussion_r919648732 ## distribution/src/assemble/component.xml: ## @@ -245,10 +245,6 @@ ../NOTICE - - ../git.properties Review Comment: @vvysotskyi thanks that slipped through because I decided to start from the existing commit in the original PR for this. > Remove non-reproducible build outputs > - > > Key: DRILL-8158 > URL: https://issues.apache.org/jira/browse/DRILL-8158 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.20.0 >Reporter: Herve Boutemy >Assignee: James Turton >Priority: Major > Fix For: 1.20.2 > > > For context see [1] and [2]. The git-commit-id plugin includes information > like build host, email and time which is not compatible with a reproducible > build. Drill's built in sys.version table will return the build email and > time if they are present in the build's git.properties file so these columns > must be deprecated. Other useful Git-related information is retained. > In accompanying commits, some Kerberos unit test fixes are applied, and the > tests reenabled, and some updates to Release.md are included. > [1] [https://maven.apache.org/guides/mini/guide-reproducible-builds.html] > [2] > [https://github.com/jvm-repo-rebuild/reproducible-central#org.apache.drill:drill-root] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DRILL-8257) Resolve Netty lib conflicts
[ https://issues.apache.org/jira/browse/DRILL-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566157#comment-17566157 ] ASF GitHub Bot commented on DRILL-8257: --- jnturton merged PR #2593: URL: https://github.com/apache/drill/pull/2593 > Resolve Netty lib conflicts > --- > > Key: DRILL-8257 > URL: https://issues.apache.org/jira/browse/DRILL-8257 > Project: Apache Drill > Issue Type: Bug > Components: library >Affects Versions: 1.20.1 >Reporter: James Turton >Assignee: James Turton >Priority: Major > Fix For: 1.20.2 > > > The following transitive dependencies conflict with Drill's own, newer Netty > dependencies and need to be excluded. > * jars/3rdparty/netty-transport-native-epoll-4.1.45.Final.jar > * jars/3rdparty/netty-all-4.1.59.Final.jar > * jars/3rdparty/netty-codec-http-4.1.59.Final.jar > It is not understood what exact conditions are needed for the library > conflict to adversely affect a Drillbit, but when they are present it becomes > impossible to enable TLS on the user RPC port. One guess is that a class > loader race condition decides whether the problem will manifest. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DRILL-8249) Parquet decoding error reading nation.dict.parquet from test framework
[
https://issues.apache.org/jira/browse/DRILL-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566155#comment-17566155
]
ASF GitHub Bot commented on DRILL-8249:
---
jnturton merged PR #2594:
URL: https://github.com/apache/drill/pull/2594
> Parquet decoding error reading nation.dict.parquet from test framework
> --
>
> Key: DRILL-8249
> URL: https://issues.apache.org/jira/browse/DRILL-8249
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Parquet
>Affects Versions: 1.20.0, 1.20.1
>Reporter: Artem Trush
>Assignee: James Turton
>Priority: Major
> Fix For: 1.20.2
>
> Attachments: nation.dict.parquet
>
>
> After one of the recent fix -
> [DRILL-1282|https://github.com/apache/drill/pull/2338] drill started to throw
> npe. Issue is related to drill 1.20 and above.
> Simple {{SELECT * FROM}} from {{nation.dict.parquet}} file. Attached it.
> Were investigated that the code
> [here|https://github.com/apache/drill/blob/master/exec/java-exec/src/main/java/org/apache/drill/exec/store/parquet/columnreaders/VarLenColumnBulkInput.java#L318L341]
> is not working as expected. Before DRILL-1282 these code lines were not used
> for reading this file (or I guess any file).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DRILL-8158) Remove non-reproducible build outputs
[ https://issues.apache.org/jira/browse/DRILL-8158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565942#comment-17565942 ] ASF GitHub Bot commented on DRILL-8158: --- vvysotskyi commented on code in PR #2590: URL: https://github.com/apache/drill/pull/2590#discussion_r919226171 ## distribution/src/assemble/component.xml: ## @@ -245,10 +245,6 @@ ../NOTICE - - ../git.properties Review Comment: Let's leave this file to be placed in the target distribution. > Remove non-reproducible build outputs > - > > Key: DRILL-8158 > URL: https://issues.apache.org/jira/browse/DRILL-8158 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.20.0 >Reporter: Herve Boutemy >Assignee: James Turton >Priority: Major > Fix For: 1.20.2 > > > For context see [1] and [2]. The git-commit-id plugin includes information > like build host, email and time which is not compatible with a reproducible > build. Drill's built in sys.version table will return the build email and > time if they are present in the build's git.properties file so these columns > must be deprecated. Other useful Git-related information is retained. > In accompanying commits, some Kerberos unit test fixes are applied, and the > tests reenabled, and some updates to Release.md are included. > [1] [https://maven.apache.org/guides/mini/guide-reproducible-builds.html] > [2] > [https://github.com/jvm-repo-rebuild/reproducible-central#org.apache.drill:drill-root] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (DRILL-8249) Parquet decoding error reading nation.dict.parquet from test framework
[
https://issues.apache.org/jira/browse/DRILL-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton reassigned DRILL-8249:
---
Assignee: James Turton (was: Artem Trush)
> Parquet decoding error reading nation.dict.parquet from test framework
> --
>
> Key: DRILL-8249
> URL: https://issues.apache.org/jira/browse/DRILL-8249
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Parquet
>Affects Versions: 1.20.0, 1.20.1
>Reporter: Artem Trush
>Assignee: James Turton
>Priority: Major
> Fix For: 1.20.2
>
> Attachments: nation.dict.parquet
>
>
> After one of the recent fix -
> [DRILL-1282|https://github.com/apache/drill/pull/2338] drill started to throw
> npe. Issue is related to drill 1.20 and above.
> Simple {{SELECT * FROM}} from {{nation.dict.parquet}} file. Attached it.
> Were investigated that the code
> [here|https://github.com/apache/drill/blob/master/exec/java-exec/src/main/java/org/apache/drill/exec/store/parquet/columnreaders/VarLenColumnBulkInput.java#L318L341]
> is not working as expected. Before DRILL-1282 these code lines were not used
> for reading this file (or I guess any file).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DRILL-8249) Parquet decoding error reading nation.dict.parquet from test framework
[
https://issues.apache.org/jira/browse/DRILL-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565465#comment-17565465
]
ASF GitHub Bot commented on DRILL-8249:
---
jnturton opened a new pull request, #2594:
URL: https://github.com/apache/drill/pull/2594
# [DRILL-8249](https://issues.apache.org/jira/browse/DRILL-8249): Parquet
decoding error reading nation.dict.parquet from test framework.
## Description
Thank you to @ArtTrush for finding and partially debugging this regression.
The Parquet test file attached to the Jira issue cannot be queried with Drill
1.20.1 because it decides from column chunk metadata that a chunk does not use
dictionary encoding and ignores new information found by the Parquet page
reader that indicates that dictionary encoding is used. This fix restores the
consideration of the `usingDictionary` flag which is updated by the page reader.
## Documentation
N/A
## Testing
The Drill Test Framework contains a test query and file nation.dict.parquet
that reveals this bug.
> Parquet decoding error reading nation.dict.parquet from test framework
> --
>
> Key: DRILL-8249
> URL: https://issues.apache.org/jira/browse/DRILL-8249
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Parquet
>Affects Versions: 1.20.0, 1.20.1
>Reporter: Artem Trush
>Assignee: Artem Trush
>Priority: Major
> Fix For: 1.20.2
>
> Attachments: nation.dict.parquet
>
>
> After one of the recent fix -
> [DRILL-1282|https://github.com/apache/drill/pull/2338] drill started to throw
> npe. Issue is related to drill 1.20 and above.
> Simple {{SELECT * FROM}} from {{nation.dict.parquet}} file. Attached it.
> Were investigated that the code
> [here|https://github.com/apache/drill/blob/master/exec/java-exec/src/main/java/org/apache/drill/exec/store/parquet/columnreaders/VarLenColumnBulkInput.java#L318L341]
> is not working as expected. Before DRILL-1282 these code lines were not used
> for reading this file (or I guess any file).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8249) Parquet decoding error reading nation.dict.parquet from test framework
[
https://issues.apache.org/jira/browse/DRILL-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton updated DRILL-8249:
Summary: Parquet decoding error reading nation.dict.parquet from test
framework (was: NullPointerException is thrown when trying select from parquet
file)
> Parquet decoding error reading nation.dict.parquet from test framework
> --
>
> Key: DRILL-8249
> URL: https://issues.apache.org/jira/browse/DRILL-8249
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Parquet
>Affects Versions: 1.20.0, 1.20.1
>Reporter: Artem Trush
>Assignee: Artem Trush
>Priority: Major
> Fix For: 1.20.2
>
> Attachments: nation.dict.parquet
>
>
> After one of the recent fix -
> [DRILL-1282|https://github.com/apache/drill/pull/2338] drill started to throw
> npe. Issue is related to drill 1.20 and above.
> Simple {{SELECT * FROM}} from {{nation.dict.parquet}} file. Attached it.
> Were investigated that the code
> [here|https://github.com/apache/drill/blob/master/exec/java-exec/src/main/java/org/apache/drill/exec/store/parquet/columnreaders/VarLenColumnBulkInput.java#L318L341]
> is not working as expected. Before DRILL-1282 these code lines were not used
> for reading this file (or I guess any file).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (DRILL-8183) Respect the ExecConstant.SSL_HANDSHAKE_TIMEOUT option
[
https://issues.apache.org/jira/browse/DRILL-8183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton closed DRILL-8183.
---
Resolution: Not A Problem
The SSL handshake timeout is applied on the client end of the connection which
is why this config option is ignored by the server end.
> Respect the ExecConstant.SSL_HANDSHAKE_TIMEOUT option
> -
>
> Key: DRILL-8183
> URL: https://issues.apache.org/jira/browse/DRILL-8183
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - RPC
>Affects Versions: 1.20.0
>Reporter: James Turton
>Assignee: James Turton
>Priority: Trivial
> Fix For: 2.0.0
>
>
> We ignore the mentioned config option and hard code this timeout to 0, which
> is interpreted by Netty as "no timeout".
> {code:java}
> @Override
> public int getHandshakeTimeout() {
> return 0;
> }{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DRILL-8257) Resolve Netty lib conflicts
[ https://issues.apache.org/jira/browse/DRILL-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565445#comment-17565445 ] ASF GitHub Bot commented on DRILL-8257: --- jnturton opened a new pull request, #2593: URL: https://github.com/apache/drill/pull/2593 # [DRILL-8257](https://issues.apache.org/jira/browse/DRILL-8257): Resolve Netty lib conflicts ## Description The following transitive dependencies in Drill 1.20.* conflict with Drill's own, newer Netty dependencies and need to be excluded. - jars/3rdparty/netty-transport-native-epoll-4.1.45.Final.jar - jars/3rdparty/netty-all-4.1.59.Final.jar - jars/3rdparty/netty-codec-http-4.1.59.Final.jar This PR introduces a Netty BOM. Note that Drill in the past picked up a dependency on every Netty component (netty-all) through the OCI HDFS connector: ``` [INFO] - > Resolve Netty lib conflicts > --- > > Key: DRILL-8257 > URL: https://issues.apache.org/jira/browse/DRILL-8257 > Project: Apache Drill > Issue Type: Bug > Components: library >Affects Versions: 1.20.1 >Reporter: James Turton >Assignee: James Turton >Priority: Major > Fix For: 1.20.2 > > > The following transitive dependencies conflict with Drill's own, newer Netty > dependencies and need to be excluded. > * jars/3rdparty/netty-transport-native-epoll-4.1.45.Final.jar > * jars/3rdparty/netty-all-4.1.59.Final.jar > * jars/3rdparty/netty-codec-http-4.1.59.Final.jar > It is not understood what exact conditions are needed for the library > conflict to adversely affect a Drillbit, but when they are present it becomes > impossible to enable TLS on the user RPC port. One guess is that a class > loader race condition decides whether the problem will manifest. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DRILL-8096) format-excel reader: support different Shared String implementations
[ https://issues.apache.org/jira/browse/DRILL-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565411#comment-17565411 ] PJ Fanning commented on DRILL-8096: --- This is not implemented. excel-streaming-reader that Drill uses does now use ReadOnlySharedStringTable so that is one part of this issue that is already addressed - but supporting allowing users to choose the implemenation when using Drill is not yet supported. The feature is potentially useful but maybe better to wait till users start reporting issues about memory footprint before adding extra Drill features. > format-excel reader: support different Shared String implementations > > > Key: DRILL-8096 > URL: https://issues.apache.org/jira/browse/DRILL-8096 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - Data Types >Reporter: PJ Fanning >Priority: Major > > One of the biggest users of memory and processing time when reading Excel > files is handling the Shared Strings Table. > excel-streaming-reader v3.3.0 supports 3 implementations. > I would suggest that Drill should use the ReadOnlySharedStringTable as the > default. > Drill currently uses the full featured Apache POI SharedStringTable by > default (which requires more memory and parsing effort). > There is also a TempFileSharedStringTable which uses a temp file to keep the > data out of heap memory. This is still pretty fast because it is implemented > using a H2 database MVMap. > If supporting allowing users configure which implementation they want sounds > useful, I can do a PR. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8257) Resolve Netty lib conflicts
[ https://issues.apache.org/jira/browse/DRILL-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8257: Description: The following transitive dependencies conflict with Drill's own, newer Netty dependencies and need to be excluded. * jars/3rdparty/netty-transport-native-epoll-4.1.45.Final.jar * jars/3rdparty/netty-all-4.1.59.Final.jar * jars/3rdparty/netty-codec-http-4.1.59.Final.jar It is not understood what exact conditions are needed for the library conflict to adversely affect a Drillbit, but when they are present it becomes impossible to enable TLS on the user RPC port. One guess is that a class loader race condition decides whether the problem will manifest. was: The following transitive dependencies conflict with Drill's own Netty dependencies and need to be excluded. jars/3rdparty/netty-transport-native-epoll-4.1.45.Final.jar jars/3rdparty/netty-all-4.1.59.Final.jar jars/3rdparty/netty-codec-http-4.1.59.Final.jar It is not understood what exact conditions are needed for the library conflict to adversely affect a Drillbit, but when they are present it becomes impossible to enable TLS on the user RPC port. One guess is that a class loader race condition decides whether the problem will manifest. > Resolve Netty lib conflicts > --- > > Key: DRILL-8257 > URL: https://issues.apache.org/jira/browse/DRILL-8257 > Project: Apache Drill > Issue Type: Bug > Components: library >Affects Versions: 1.20.1 >Reporter: James Turton >Assignee: James Turton >Priority: Major > Fix For: 1.20.2 > > > The following transitive dependencies conflict with Drill's own, newer Netty > dependencies and need to be excluded. > * jars/3rdparty/netty-transport-native-epoll-4.1.45.Final.jar > * jars/3rdparty/netty-all-4.1.59.Final.jar > * jars/3rdparty/netty-codec-http-4.1.59.Final.jar > It is not understood what exact conditions are needed for the library > conflict to adversely affect a Drillbit, but when they are present it becomes > impossible to enable TLS on the user RPC port. One guess is that a class > loader race condition decides whether the problem will manifest. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DRILL-8257) Resolve Netty lib conflicts
James Turton created DRILL-8257: --- Summary: Resolve Netty lib conflicts Key: DRILL-8257 URL: https://issues.apache.org/jira/browse/DRILL-8257 Project: Apache Drill Issue Type: Bug Components: library Affects Versions: 1.20.1 Reporter: James Turton Assignee: James Turton Fix For: 1.20.2 The following transitive dependencies conflict with Drill's own Netty dependencies and need to be excluded. jars/3rdparty/netty-transport-native-epoll-4.1.45.Final.jar jars/3rdparty/netty-all-4.1.59.Final.jar jars/3rdparty/netty-codec-http-4.1.59.Final.jar It is not understood what exact conditions are needed for the library conflict to adversely affect a Drillbit, but when they are present it becomes impossible to enable TLS on the user RPC port. One guess is that a class loader race condition decides whether the problem will manifest. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-7978) Fixed Width Format Plugin
[ https://issues.apache.org/jira/browse/DRILL-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-7978: Fix Version/s: 2.0.0 > Fixed Width Format Plugin > - > > Key: DRILL-7978 > URL: https://issues.apache.org/jira/browse/DRILL-7978 > Project: Apache Drill > Issue Type: New Feature > Components: Storage - Other >Reporter: Megan Foss >Priority: Major > Fix For: 2.0.0 > > > Developing format plugin to parse fixed width files. > Fixed Width Text File Definition: > https://www.oracle.com/webfolder/technetwork/data-quality/edqhelp/Content/introduction/getting_started/configuring_fixed_width_text_file_formats.htm -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8036) Enable Spnego and Kerberos Tests
[ https://issues.apache.org/jira/browse/DRILL-8036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8036. --- Resolution: Duplicate > Enable Spnego and Kerberos Tests > > > Key: DRILL-8036 > URL: https://issues.apache.org/jira/browse/DRILL-8036 > Project: Apache Drill > Issue Type: Improvement > Components: Security >Affects Versions: 1.19.0 >Reporter: Vitalii Diravka >Assignee: Vitalii Diravka >Priority: Major > > DRILL-5387 disables several test cases. Since that time Hadoop lib was > updated, so enabling test cases should be reconsidered. Besides that disabled > test cases create uncertainty about that specific functionality -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8088) Improve expression evaluation performance
[ https://issues.apache.org/jira/browse/DRILL-8088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8088. --- Resolution: Fixed > Improve expression evaluation performance > - > > Key: DRILL-8088 > URL: https://issues.apache.org/jira/browse/DRILL-8088 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - Codegen >Affects Versions: 1.19.0 >Reporter: wtf >Assignee: wtf >Priority: Minor > Fix For: 1.20.0 > > > Found unnecessary map copy when doing expression evaluation, it will slow > down the codegen when the query include many "case when" or avg/stddev(the > reduced expressions include "case when"). In our case, the query include 314 > avg, it takes 3+ seconds to generate the projector expressions(Intel(R) > Xeon(R) CPU E5-2682 v4 @ 2.50GHz 32cores). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8088) Improve expression evaluation performance
[ https://issues.apache.org/jira/browse/DRILL-8088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8088: Affects Version/s: 1.19.0 > Improve expression evaluation performance > - > > Key: DRILL-8088 > URL: https://issues.apache.org/jira/browse/DRILL-8088 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - Codegen >Affects Versions: 1.19.0 >Reporter: wtf >Assignee: wtf >Priority: Minor > Fix For: 1.20.0 > > > Found unnecessary map copy when doing expression evaluation, it will slow > down the codegen when the query include many "case when" or avg/stddev(the > reduced expressions include "case when"). In our case, the query include 314 > avg, it takes 3+ seconds to generate the projector expressions(Intel(R) > Xeon(R) CPU E5-2682 v4 @ 2.50GHz 32cores). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8088) Improve expression evaluation performance
[ https://issues.apache.org/jira/browse/DRILL-8088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8088: Fix Version/s: 1.20.0 > Improve expression evaluation performance > - > > Key: DRILL-8088 > URL: https://issues.apache.org/jira/browse/DRILL-8088 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - Codegen >Reporter: wtf >Assignee: wtf >Priority: Minor > Fix For: 1.20.0 > > > Found unnecessary map copy when doing expression evaluation, it will slow > down the codegen when the query include many "case when" or avg/stddev(the > reduced expressions include "case when"). In our case, the query include 314 > avg, it takes 3+ seconds to generate the projector expressions(Intel(R) > Xeon(R) CPU E5-2682 v4 @ 2.50GHz 32cores). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8094) Support reverse truncation for split_part udf
[
https://issues.apache.org/jira/browse/DRILL-8094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton updated DRILL-8094:
Fix Version/s: 1.20.0
> Support reverse truncation for split_part udf
> -
>
> Key: DRILL-8094
> URL: https://issues.apache.org/jira/browse/DRILL-8094
> Project: Apache Drill
> Issue Type: Improvement
>Affects Versions: 1.19.0
>Reporter: wtf
>Priority: Minor
> Fix For: 1.20.0
>
>
> suport split_part('a,b,c,d', ',' , -2, -1) = 'c,d' and split_part('a,b,c,d',
> ',' , -3) = 'b'
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8094) Support reverse truncation for split_part udf
[
https://issues.apache.org/jira/browse/DRILL-8094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton updated DRILL-8094:
Affects Version/s: 1.19.0
> Support reverse truncation for split_part udf
> -
>
> Key: DRILL-8094
> URL: https://issues.apache.org/jira/browse/DRILL-8094
> Project: Apache Drill
> Issue Type: Improvement
>Affects Versions: 1.19.0
>Reporter: wtf
>Priority: Minor
>
> suport split_part('a,b,c,d', ',' , -2, -1) = 'c,d' and split_part('a,b,c,d',
> ',' , -3) = 'b'
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (DRILL-8094) Support reverse truncation for split_part udf
[
https://issues.apache.org/jira/browse/DRILL-8094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton closed DRILL-8094.
---
Resolution: Fixed
> Support reverse truncation for split_part udf
> -
>
> Key: DRILL-8094
> URL: https://issues.apache.org/jira/browse/DRILL-8094
> Project: Apache Drill
> Issue Type: Improvement
>Affects Versions: 1.19.0
>Reporter: wtf
>Priority: Minor
> Fix For: 1.20.0
>
>
> suport split_part('a,b,c,d', ',' , -2, -1) = 'c,d' and split_part('a,b,c,d',
> ',' , -3) = 'b'
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DRILL-8096) format-excel reader: support different Shared String implementations
[ https://issues.apache.org/jira/browse/DRILL-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565329#comment-17565329 ] James Turton commented on DRILL-8096: - Hi [~pj.fanning], [~cgivre] is this issue still open or can we close it? > format-excel reader: support different Shared String implementations > > > Key: DRILL-8096 > URL: https://issues.apache.org/jira/browse/DRILL-8096 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - Data Types >Reporter: PJ Fanning >Priority: Major > > One of the biggest users of memory and processing time when reading Excel > files is handling the Shared Strings Table. > excel-streaming-reader v3.3.0 supports 3 implementations. > I would suggest that Drill should use the ReadOnlySharedStringTable as the > default. > Drill currently uses the full featured Apache POI SharedStringTable by > default (which requires more memory and parsing effort). > There is also a TempFileSharedStringTable which uses a temp file to keep the > data out of heap memory. This is still pretty fast because it is implemented > using a H2 database MVMap. > If supporting allowing users configure which implementation they want sounds > useful, I can do a PR. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DRILL-8098) Error starting Drill (drill-embedded) 1.20.0 on ppc64le
[
https://issues.apache.org/jira/browse/DRILL-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565327#comment-17565327
]
James Turton commented on DRILL-8098:
-
Hi [~makino], the benefit of [~luoc]'s suggestion would be to remove the SQL
client software sqlline from the picture so that we could tell if Drill itself
starts okay. You do not need to add more nodes to start Drill in cluster mode,
you only need to start up a ZooKeeper using its default config and launch Drill
with drillbit.sh instead of drill-embedded. It can all be done on one machine
and is quite straightforward.
> Error starting Drill (drill-embedded) 1.20.0 on ppc64le
> ---
>
> Key: DRILL-8098
> URL: https://issues.apache.org/jira/browse/DRILL-8098
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - CLI
>Affects Versions: 1.20.0
> Environment: Apache Drill 1.20.0 on Debian Bullseye ppc64le with
> Apache Maven 3.6.3 and OpenJDK 11.0.13
>Reporter: makino
>Priority: Minor
>
> Building Drill as described in [Compiling Drill from
> Source|https://drill.apache.org/docs/compiling-drill-from-source/] via
> {{mvn clean install -DskipTests}}
> I am able to start drill-embedded, however the CLI (apache drill>) is not
> responding, nor showing any errors. In order to exit drill-embedded I have to
> forcefully stop the session. There is no matching description on
> [Troubleshooting|https://drill.apache.org/docs/troubleshooting/]. Is there
> anything I can do to further debug this or provide more information to
> analyze the error?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (DRILL-8098) Error starting Drill (drill-embedded) 1.20.0 on ppc64le
[
https://issues.apache.org/jira/browse/DRILL-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565327#comment-17565327
]
James Turton edited comment on DRILL-8098 at 7/12/22 7:24 AM:
--
Hi [~makino], the benefit of [~luoc]'s suggestion would be to remove the SQL
client software sqlline from the picture so that we could tell if Drill itself
starts okay. You do not need to add more nodes to start Drill in cluster mode,
you only need to start up a ZooKeeper using its default config and launch Drill
with drillbit.sh instead of drill-embedded. It can all be done on one machine
and is quite straightforward. Any more tests you can run would be helpful for
us since we aren't able to test on this arch ourselves.
was (Author: dzamo):
Hi [~makino], the benefit of [~luoc]'s suggestion would be to remove the SQL
client software sqlline from the picture so that we could tell if Drill itself
starts okay. You do not need to add more nodes to start Drill in cluster mode,
you only need to start up a ZooKeeper using its default config and launch Drill
with drillbit.sh instead of drill-embedded. It can all be done on one machine
and is quite straightforward.
> Error starting Drill (drill-embedded) 1.20.0 on ppc64le
> ---
>
> Key: DRILL-8098
> URL: https://issues.apache.org/jira/browse/DRILL-8098
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - CLI
>Affects Versions: 1.20.0
> Environment: Apache Drill 1.20.0 on Debian Bullseye ppc64le with
> Apache Maven 3.6.3 and OpenJDK 11.0.13
>Reporter: makino
>Priority: Minor
>
> Building Drill as described in [Compiling Drill from
> Source|https://drill.apache.org/docs/compiling-drill-from-source/] via
> {{mvn clean install -DskipTests}}
> I am able to start drill-embedded, however the CLI (apache drill>) is not
> responding, nor showing any errors. In order to exit drill-embedded I have to
> forcefully stop the session. There is no matching description on
> [Troubleshooting|https://drill.apache.org/docs/troubleshooting/]. Is there
> anything I can do to further debug this or provide more information to
> analyze the error?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DRILL-8185) EVF 2 doen't handle map arrays or nested maps
[ https://issues.apache.org/jira/browse/DRILL-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565323#comment-17565323 ] Paul Rogers commented on DRILL-8185: Sorry for the delay on this one. Am chipping away writing unit tests, trying to track down which "dummy" writers are missing. > EVF 2 doen't handle map arrays or nested maps > - > > Key: DRILL-8185 > URL: https://issues.apache.org/jira/browse/DRILL-8185 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.20.0 >Reporter: Paul Rogers >Assignee: Paul Rogers >Priority: Major > Fix For: 2.0.0 > > > When converting Avro, Luoc found two bugs in how EVF 2 (the projection > mechanism) handles map array and nested maps -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8255) Update Drill-Calcite version to include fix for CALCITE-4992
[ https://issues.apache.org/jira/browse/DRILL-8255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8255. --- Resolution: Fixed > Update Drill-Calcite version to include fix for CALCITE-4992 > > > Key: DRILL-8255 > URL: https://issues.apache.org/jira/browse/DRILL-8255 > Project: Apache Drill > Issue Type: Task >Affects Versions: 1.20.1 >Reporter: Vova Vysotskyi >Assignee: Vova Vysotskyi >Priority: Major > Fix For: 1.20.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8255) Update Drill-Calcite version to include fix for CALCITE-4992
[ https://issues.apache.org/jira/browse/DRILL-8255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8255: Fix Version/s: 1.20.2 > Update Drill-Calcite version to include fix for CALCITE-4992 > > > Key: DRILL-8255 > URL: https://issues.apache.org/jira/browse/DRILL-8255 > Project: Apache Drill > Issue Type: Task >Affects Versions: 1.20.1 >Reporter: Vova Vysotskyi >Assignee: Vova Vysotskyi >Priority: Major > Fix For: 1.20.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (DRILL-8256) Fix unit tests of Kerberos auth in RPC
[ https://issues.apache.org/jira/browse/DRILL-8256 ] James Turton deleted comment on DRILL-8256: - was (Author: githubbot): jnturton commented on PR #2592: URL: https://github.com/apache/drill/pull/2592#issuecomment-1181372678 Weird, the TestBitBitKerberos class isn't being run even though I've removed the @Ignore from it. Yet there's another class in the same package called TestBitRpc which _is_ run. @vdiravka, any idea why this is happening? Is it because I converted TestBitBitKerberos to a ClusterTest? > Fix unit tests of Kerberos auth in RPC > --- > > Key: DRILL-8256 > URL: https://issues.apache.org/jira/browse/DRILL-8256 > Project: Apache Drill > Issue Type: Bug > Components: Security >Affects Versions: 1.20.1 >Reporter: James Turton >Assignee: James Turton >Priority: Minor > Fix For: 1.20.2 > > > Minor bugs in some unit tests in org.apache.drill.exec.rpc.user.security have > meant that they have been disabled historically to prevent causing CI > failures. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8254) upgrade mysql-connectors-java to 8.0.28 due to CVE-2022-21363
[ https://issues.apache.org/jira/browse/DRILL-8254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8254. --- Resolution: Fixed > upgrade mysql-connectors-java to 8.0.28 due to CVE-2022-21363 > - > > Key: DRILL-8254 > URL: https://issues.apache.org/jira/browse/DRILL-8254 > Project: Apache Drill > Issue Type: Bug >Reporter: Jingchuan Hu >Priority: Major > Fix For: 1.20.2 > > > Upgrade MySQL Connectors JAVA to 8.0.28 due to CVE-2022-21363 > [https://github.com/advisories/GHSA-g76j-4cxx-23h9] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8255) Update Drill-Calcite version to include fix for CALCITE-4992
[ https://issues.apache.org/jira/browse/DRILL-8255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8255: Affects Version/s: 1.20.1 > Update Drill-Calcite version to include fix for CALCITE-4992 > > > Key: DRILL-8255 > URL: https://issues.apache.org/jira/browse/DRILL-8255 > Project: Apache Drill > Issue Type: Task >Affects Versions: 1.20.1 >Reporter: Vova Vysotskyi >Assignee: Vova Vysotskyi >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8253) Support the limit results in kafka scan
[ https://issues.apache.org/jira/browse/DRILL-8253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8253. --- Resolution: Fixed > Support the limit results in kafka scan > --- > > Key: DRILL-8253 > URL: https://issues.apache.org/jira/browse/DRILL-8253 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - Kafka >Reporter: Cong Luo >Assignee: Cong Luo >Priority: Major > Fix For: 1.20.2 > > > In the current implementation of the kafka storage, although we use the limit > detection method in the result loader, but the actual *maxRecords* is always > -1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8254) upgrade mysql-connectors-java to 8.0.28 due to CVE-2022-21363
[ https://issues.apache.org/jira/browse/DRILL-8254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8254: Fix Version/s: 1.20.2 > upgrade mysql-connectors-java to 8.0.28 due to CVE-2022-21363 > - > > Key: DRILL-8254 > URL: https://issues.apache.org/jira/browse/DRILL-8254 > Project: Apache Drill > Issue Type: Bug >Reporter: Jingchuan Hu >Priority: Major > Fix For: 1.20.2 > > > Upgrade MySQL Connectors JAVA to 8.0.28 due to CVE-2022-21363 > [https://github.com/advisories/GHSA-g76j-4cxx-23h9] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8251) Upgrade hadoop 2 (to 2.10.2) due to CVE
[ https://issues.apache.org/jira/browse/DRILL-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8251. --- Resolution: Fixed > Upgrade hadoop 2 (to 2.10.2) due to CVE > > > Key: DRILL-8251 > URL: https://issues.apache.org/jira/browse/DRILL-8251 > Project: Apache Drill > Issue Type: Improvement >Affects Versions: 1.20.1 >Reporter: PJ Fanning >Priority: Major > Fix For: 1.20.2 > > > Relates to https://github.com/apache/drill/security/dependabot/21 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8251) Upgrade hadoop 2 (to 2.10.2) due to CVE
[ https://issues.apache.org/jira/browse/DRILL-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8251: Fix Version/s: 1.20.2 > Upgrade hadoop 2 (to 2.10.2) due to CVE > > > Key: DRILL-8251 > URL: https://issues.apache.org/jira/browse/DRILL-8251 > Project: Apache Drill > Issue Type: Improvement >Affects Versions: 1.20.1 >Reporter: PJ Fanning >Priority: Major > Fix For: 1.20.2 > > > Relates to https://github.com/apache/drill/security/dependabot/21 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8244) HTTP_Request Not Passing Down Config Variable
[ https://issues.apache.org/jira/browse/DRILL-8244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8244. --- > HTTP_Request Not Passing Down Config Variable > - > > Key: DRILL-8244 > URL: https://issues.apache.org/jira/browse/DRILL-8244 > Project: Apache Drill > Issue Type: Bug > Components: Storage - Other >Affects Versions: 1.20.1 >Reporter: Charles Givre >Assignee: Charles Givre >Priority: Major > Fix For: 2.0.0 > > > The http_request UDF was not passing down the provided schema and other > config parameters down to the jsonLoader. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8243) Move JSON Config Options Out of HTTP Plugin
[ https://issues.apache.org/jira/browse/DRILL-8243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8243. --- Resolution: Fixed > Move JSON Config Options Out of HTTP Plugin > --- > > Key: DRILL-8243 > URL: https://issues.apache.org/jira/browse/DRILL-8243 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - JSON >Affects Versions: 1.20.1 >Reporter: Charles Givre >Assignee: Charles Givre >Priority: Minor > Fix For: 2.0.0 > > > As part of DRILL-8241, this PR moves the json configuration options out of > the HTTP plugin and creates a file which can be used for other plugins that > consume JSON data. > The idea being that all such plugins, like Druid, ES, Mongo, can set the same > JSON options for each plugin instance w/o having to duplicate config code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8231) Wrong result in the COUNT function position.
[
https://issues.apache.org/jira/browse/DRILL-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton updated DRILL-8231:
Affects Version/s: 1.19.0
> Wrong result in the COUNT function position.
>
>
> Key: DRILL-8231
> URL: https://issues.apache.org/jira/browse/DRILL-8231
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.18.0, 1.19.0
>Reporter: manabu nagamine
>Priority: Major
> Fix For: 1.20.2
>
> Attachments: drill.zip
>
>
> Hi Team.
> We using Drill 1.18.
> There is a phenomenon that the count values of COL4452 are different in the
> execution results of the following queries.
> The only difference is that the positions of COL4452 and COL6408 have been
> changed.
> {code:java}
> 1.
> select COUNT(DISTINCT val2) COL4452, SUM(CAST(val11 as BIGINT)+CAST(val12 as
> BIGINT)) COL6408 from dfs.root.`/drill/data/*/log_15872_R_79_*.parquet` WHERE
> 1 = 1 and ( ( dir0 between '01' and '10' ) ) and ( LOG_DATE >= '2022-04-01
> 00:00:00.00' and LOG_DATE <= '2022-04-30 23:59:59.00');
> 2.
> select SUM(CAST(val11 as BIGINT)+CAST(val12 as BIGINT)) COL6408,
> COUNT(DISTINCT val2) COL4452 from
> dfs.root.`/drill/data/*/log_15872_R_79_*.parquet` WHERE 1 = 1 and ( ( dir0
> between '01' and '10' ) ) and ( LOG_DATE >= '2022-04-01 00:00:00.00' and
> LOG_DATE <= '2022-04-30 23:59:59.00');{code}
> As for the actual data, the count with COL4452 at the beginning of 1. is
> correct.
> I am having trouble understanding the cause of this phenomenon.
> Can anybody help me?Thanks in advance.
> Attached the parquet log file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (DRILL-8202) Add Options to Skip Malformed JSON Records to HTTP Plugin
[ https://issues.apache.org/jira/browse/DRILL-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8202. --- Resolution: Fixed > Add Options to Skip Malformed JSON Records to HTTP Plugin > - > > Key: DRILL-8202 > URL: https://issues.apache.org/jira/browse/DRILL-8202 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - Other >Affects Versions: 1.20.0 >Reporter: Charles Givre >Assignee: Charles Givre >Priority: Major > Fix For: 2.0.0 > > > The JSON reader has the possibility of skipping malformed records and > documents, but this is a global setting. This PR adds this configuration to > the HTTP plugin so that it can be set individually for each endpoint. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8199) Convert Excel EVF1 to EVF2
[ https://issues.apache.org/jira/browse/DRILL-8199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8199. --- Resolution: Fixed > Convert Excel EVF1 to EVF2 > -- > > Key: DRILL-8199 > URL: https://issues.apache.org/jira/browse/DRILL-8199 > Project: Apache Drill > Issue Type: Sub-task > Components: Storage - Excel >Affects Versions: 1.20.1 >Reporter: Vitalii Diravka >Assignee: James Turton >Priority: Major > Fix For: 2.0.0 > > > EVF1 is currently implemented. Need to udpate to EVF2 > _ScanFrameworkVersion#EVF_V2_ > (DRILL-8085) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8185) EVF 2 doen't handle map arrays or nested maps
[ https://issues.apache.org/jira/browse/DRILL-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8185: Fix Version/s: 2.0.0 > EVF 2 doen't handle map arrays or nested maps > - > > Key: DRILL-8185 > URL: https://issues.apache.org/jira/browse/DRILL-8185 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.20.0 >Reporter: Paul Rogers >Assignee: Paul Rogers >Priority: Major > Fix For: 2.0.0 > > > When converting Avro, Luoc found two bugs in how EVF 2 (the projection > mechanism) handles map array and nested maps -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8189) Convert Image format to EVF2
[ https://issues.apache.org/jira/browse/DRILL-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8189: Fix Version/s: 2.0.0 > Convert Image format to EVF2 > > > Key: DRILL-8189 > URL: https://issues.apache.org/jira/browse/DRILL-8189 > Project: Apache Drill > Issue Type: Improvement >Affects Versions: 1.20.0 >Reporter: Cong Luo >Assignee: Cong Luo >Priority: Major > Fix For: 2.0.0 > > > Second refactor of the Image format. > In addition, continue to deal with minor bugs in the V2 framework. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8188) Convert HDF5 format to EVF2
[ https://issues.apache.org/jira/browse/DRILL-8188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8188: Fix Version/s: 2.0.0 > Convert HDF5 format to EVF2 > --- > > Key: DRILL-8188 > URL: https://issues.apache.org/jira/browse/DRILL-8188 > Project: Apache Drill > Issue Type: Improvement >Affects Versions: 1.20.0 >Reporter: Cong Luo >Assignee: Cong Luo >Priority: Major > Fix For: 2.0.0 > > > Use EVF V2 instead of old V1. > Also, fixed a few bugs in V2 framework. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8179) Convert LTSV Format Plugin to EVF2
[ https://issues.apache.org/jira/browse/DRILL-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8179: Affects Version/s: 1.20.1 > Convert LTSV Format Plugin to EVF2 > -- > > Key: DRILL-8179 > URL: https://issues.apache.org/jira/browse/DRILL-8179 > Project: Apache Drill > Issue Type: Improvement >Affects Versions: 1.20.1 >Reporter: Jingchuan Hu >Priority: Major > Fix For: 2.0.0 > > > Get authorized by Charles, continue the conversion from LTSV to EVF2 directly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8182) File scan nodes not differentiated by format config
[
https://issues.apache.org/jira/browse/DRILL-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton closed DRILL-8182.
---
Resolution: Fixed
> File scan nodes not differentiated by format config
> ---
>
> Key: DRILL-8182
> URL: https://issues.apache.org/jira/browse/DRILL-8182
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Other
>Affects Versions: 1.20.0
>Reporter: James Turton
>Assignee: Charles Givre
>Priority: Major
> Fix For: 1.20.2
>
> Attachments: Products_Customers_Orders.xlsx
>
>
> Two file scans that differ only by format config overriden with table
> functions may be genuinely different in terms of the data they return. The
> format config options may affect the behaviour of the format parser (date
> strings, delimiters, etc.) possibly directing format plugin to entirely
> different data within the file. Such scans should not be considered the same
> by the query planner. This illustrated by the following example based on the
> Excel format plugin.
> When a query includes multiple SELECTs against a workbook by using TABLE
> functions to access different sheets, and those sheets contain a column with
> the same name, then values for that column come a single sheet for both
> SELECTs. To reproduce, run the following query against the attachment and
> note that the `Name` values returned from the Products sheet are `Name`
> values from the Customers sheet.
>
> {code:java}
> with
> prod as (
> select Id, Name from TABLE(dfs.tmp.`/Products_Customers_Orders.xlsx`
> (type => 'excel', sheetName => 'Products'))
> )
> , cust as (
> select Id, Name from TABLE(dfs.tmp.`/Products_Customers_Orders.xlsx`
> (type => 'excel', sheetName => 'Customers'))
> )
> select * from cust join prod on cust.Id = prod.Id; {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8173) Replace httpcomponents by okhttp
[ https://issues.apache.org/jira/browse/DRILL-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8173: Priority: Minor (was: Major) > Replace httpcomponents by okhttp > > > Key: DRILL-8173 > URL: https://issues.apache.org/jira/browse/DRILL-8173 > Project: Apache Drill > Issue Type: Improvement >Affects Versions: 1.20.1 >Reporter: Jingchuan Hu >Priority: Minor > Fix For: 2.0.0 > > > The newest httpcomponent version is 5.5, however, the version used by drill > is 4.1.4, actually is a little bit out of date. Besides, the more popular > tool is okhttp, which is also adopted by drill. So I will replace all usages > of httpcomponent to okhttp, for dependency optimization purposes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8179) Convert LTSV Format Plugin to EVF2
[ https://issues.apache.org/jira/browse/DRILL-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8179: Fix Version/s: 2.0.0 > Convert LTSV Format Plugin to EVF2 > -- > > Key: DRILL-8179 > URL: https://issues.apache.org/jira/browse/DRILL-8179 > Project: Apache Drill > Issue Type: Improvement >Reporter: Jingchuan Hu >Priority: Major > Fix For: 2.0.0 > > > Get authorized by Charles, continue the conversion from LTSV to EVF2 directly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8173) Replace httpcomponents by okhttp
[ https://issues.apache.org/jira/browse/DRILL-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8173: Fix Version/s: 2.0.0 > Replace httpcomponents by okhttp > > > Key: DRILL-8173 > URL: https://issues.apache.org/jira/browse/DRILL-8173 > Project: Apache Drill > Issue Type: Improvement >Reporter: Jingchuan Hu >Priority: Major > Fix For: 2.0.0 > > > The newest httpcomponent version is 5.5, however, the version used by drill > is 4.1.4, actually is a little bit out of date. Besides, the more popular > tool is okhttp, which is also adopted by drill. So I will replace all usages > of httpcomponent to okhttp, for dependency optimization purposes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8173) Replace httpcomponents by okhttp
[ https://issues.apache.org/jira/browse/DRILL-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8173: Affects Version/s: 1.20.1 > Replace httpcomponents by okhttp > > > Key: DRILL-8173 > URL: https://issues.apache.org/jira/browse/DRILL-8173 > Project: Apache Drill > Issue Type: Improvement >Affects Versions: 1.20.1 >Reporter: Jingchuan Hu >Priority: Major > Fix For: 2.0.0 > > > The newest httpcomponent version is 5.5, however, the version used by drill > is 4.1.4, actually is a little bit out of date. Besides, the more popular > tool is okhttp, which is also adopted by drill. So I will replace all usages > of httpcomponent to okhttp, for dependency optimization purposes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8170) Use the new Liquibase feature to override the obsolete feature
[
https://issues.apache.org/jira/browse/DRILL-8170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton updated DRILL-8170:
Affects Version/s: 1.20.1
> Use the new Liquibase feature to override the obsolete feature
> --
>
> Key: DRILL-8170
> URL: https://issues.apache.org/jira/browse/DRILL-8170
> Project: Apache Drill
> Issue Type: Improvement
>Affects Versions: 1.20.1
>Reporter: Cong Luo
>Priority: Minor
>
> *[Very minor, but can be good for newcomers]*
> It is recommended to use the new function if the following issue is resolved.
> [https://github.com/liquibase/liquibase/issues/2349]
> {code:java}
> // Deprecated
> DatabaseFactory.getInstance()
> // New
> Scope.getCurrentScope().getSingleton(DatabaseFactory.class){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (DRILL-8149) format-excel plugin needs to support POI IOUtils byte array overrides to support big files
[ https://issues.apache.org/jira/browse/DRILL-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8149. --- Resolution: Fixed > format-excel plugin needs to support POI IOUtils byte array overrides to > support big files > -- > > Key: DRILL-8149 > URL: https://issues.apache.org/jira/browse/DRILL-8149 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - Data Types >Affects Versions: 1.19.0 >Reporter: PJ Fanning >Priority: Major > Fix For: 2.0.0 > > > [https://poi.apache.org/components/configuration.html] - see > [org.apache.poi.util.IOUtils.setByteArrayMaxOverride(int > maxOverride)|https://poi.apache.org/apidocs/5.0/org/apache/poi/util/IOUtils.html#setByteArrayMaxOverride-int-] > Core POI code tries to set limits on resource allocations. > excel-streaming-reader may not be as heavily affected by these settings > because it only used parts of the core POI codebase. > POI 5.2.1 (due in next few weeks) fixes a few issues but there is some > evidence that core POI users are hitting issues when loading large files and > having to set the byte array max override setting. > I can do some testing of the format-excel plugin to see if it can hit these > issues with large files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8149) format-excel plugin needs to support POI IOUtils byte array overrides to support big files
[ https://issues.apache.org/jira/browse/DRILL-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8149: Fix Version/s: 2.0.0 > format-excel plugin needs to support POI IOUtils byte array overrides to > support big files > -- > > Key: DRILL-8149 > URL: https://issues.apache.org/jira/browse/DRILL-8149 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - Data Types >Affects Versions: 1.19.0 >Reporter: PJ Fanning >Priority: Major > Fix For: 2.0.0 > > > [https://poi.apache.org/components/configuration.html] - see > [org.apache.poi.util.IOUtils.setByteArrayMaxOverride(int > maxOverride)|https://poi.apache.org/apidocs/5.0/org/apache/poi/util/IOUtils.html#setByteArrayMaxOverride-int-] > Core POI code tries to set limits on resource allocations. > excel-streaming-reader may not be as heavily affected by these settings > because it only used parts of the core POI codebase. > POI 5.2.1 (due in next few weeks) fixes a few issues but there is some > evidence that core POI users are hitting issues when loading large files and > having to set the byte array max override setting. > I can do some testing of the format-excel plugin to see if it can hit these > issues with large files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (DRILL-8136) Overhaul implict type cast system
[
https://issues.apache.org/jira/browse/DRILL-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton reassigned DRILL-8136:
---
Assignee: James Turton
> Overhaul implict type cast system
> -
>
> Key: DRILL-8136
> URL: https://issues.apache.org/jira/browse/DRILL-8136
> Project: Apache Drill
> Issue Type: Improvement
>Reporter: Esther Buchwalter
>Assignee: James Turton
>Priority: Minor
>
> The existing implicit casting system is built on simplistic total ordering of
> data types that yields oddities such as TINYINT being regarded as the closest
> numeric type to VARCHAR. This, in turn, hurts the range of data types with
> which SQL functions can be used. E.g. `select sqrt('3.1415926')` works in
> many RDBMSes, and will in Drill too if we improve the implcit casting system.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8136) Overhaul implict type cast system
[
https://issues.apache.org/jira/browse/DRILL-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton updated DRILL-8136:
Description: The existing implicit casting system is built on simplistic
total ordering of data types that yields oddities such as TINYINT being
regarded as the closest numeric type to VARCHAR. This, in turn, hurts the range
of data types with which SQL functions can be used. E.g. `select
sqrt('3.1415926')` works in many RDBMSes, and will in Drill too if we improve
the implcit casting system. (was: Additional UDFs to overload existing Math
functions in Drill so that Math UDFs accept input in type VARCHAR.)
> Overhaul implict type cast system
> -
>
> Key: DRILL-8136
> URL: https://issues.apache.org/jira/browse/DRILL-8136
> Project: Apache Drill
> Issue Type: Improvement
>Reporter: Esther Buchwalter
>Priority: Minor
>
> The existing implicit casting system is built on simplistic total ordering of
> data types that yields oddities such as TINYINT being regarded as the closest
> numeric type to VARCHAR. This, in turn, hurts the range of data types with
> which SQL functions can be used. E.g. `select sqrt('3.1415926')` works in
> many RDBMSes, and will in Drill too if we improve the implcit casting system.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8136) Overhaul implict type cast system
[ https://issues.apache.org/jira/browse/DRILL-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8136: Summary: Overhaul implict type cast system (was: Overload Scalar Math Functions) > Overhaul implict type cast system > - > > Key: DRILL-8136 > URL: https://issues.apache.org/jira/browse/DRILL-8136 > Project: Apache Drill > Issue Type: Improvement >Reporter: Esther Buchwalter >Priority: Minor > > Additional UDFs to overload existing Math functions in Drill so that Math > UDFs accept input in type VARCHAR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8135) Option to prevent Impersonation for Metastore
[
https://issues.apache.org/jira/browse/DRILL-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton updated DRILL-8135:
Fix Version/s: 2.0.0
> Option to prevent Impersonation for Metastore
> -
>
> Key: DRILL-8135
> URL: https://issues.apache.org/jira/browse/DRILL-8135
> Project: Apache Drill
> Issue Type: Improvement
> Components: Metadata
>Affects Versions: 1.20.0
> Environment: * drill-1.20.0-hadoop2
> * hadoop 2.9.2
> * ranger 1.2.0
>Reporter: Christian Pfarr
>Priority: Minor
> Labels: iceberg, metastore
> Fix For: 2.0.0
>
> Attachments: analyze-table-refresh-metadata.json
>
>
> After enabling iceberg metastore within a kerberized hadoop cluster and
> enabled impersonation, i have to give all users full access to the metastore
> directory in hdfs.
> If not, i get an _Permission denied_ when a non-admistator tries to call
> {code:java}
> analyze table hdfs.`dataset` refresh metadata{code}
> I attached the profile with the permission denied error from hdfs/ranger.
> Im not sure if i should call this a bug, because drill should impersonate
> everything, and so its also impersonating the iceberg metastore. But as an
> admin i dont want to give all users full write access to the metastore. A
> unexperienced user could accidentally overwrite something and corrupt the
> iceberg table or delete metadata completly.
> Maybe we could add a option to drill-metastore-overwrite.conf
> {code:java}
> drill.metastore: {
> implementation.class: "org.apache.drill.metastore.iceberg.IcebergMetastore",
> iceberg: {
> location: {
> relative_path: "hdfs://nameservice/drill-metastore"
> },
> impersonation: {
> enabled: true,
> max_chained_user_hops: 3
> }
> }
> }{code}
> In my case, i would of course disable it, but to match the behaviour of the
> general impersonation it could look like this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8132) Improvement of RPC
[ https://issues.apache.org/jira/browse/DRILL-8132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8132: Fix Version/s: 2.0.0 > Improvement of RPC > -- > > Key: DRILL-8132 > URL: https://issues.apache.org/jira/browse/DRILL-8132 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - RPC >Affects Versions: 1.20.1 >Reporter: wtf >Assignee: wtf >Priority: Minor > Fix For: 2.0.0 > > > # Separate EventLoopGroup between dataserver and control client/server, as > the node which is busy on receiving data from different nodes may occupy all > EventLoopGroup threads, will block the control rpc message, e.g. fragment > transfer. > # Change the default threads of EventLoopGroup to 8(current is 10), as it > can improve performance if the number is power of two based on > PowerOfTwoEventExecutorChooser of Netty. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8132) Improvement of RPC
[ https://issues.apache.org/jira/browse/DRILL-8132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8132. --- Resolution: Fixed > Improvement of RPC > -- > > Key: DRILL-8132 > URL: https://issues.apache.org/jira/browse/DRILL-8132 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - RPC >Affects Versions: 1.20.1 >Reporter: wtf >Assignee: wtf >Priority: Minor > Fix For: 2.0.0 > > > # Separate EventLoopGroup between dataserver and control client/server, as > the node which is busy on receiving data from different nodes may occupy all > EventLoopGroup threads, will block the control rpc message, e.g. fragment > transfer. > # Change the default threads of EventLoopGroup to 8(current is 10), as it > can improve performance if the number is power of two based on > PowerOfTwoEventExecutorChooser of Netty. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8132) Improvement of RPC
[ https://issues.apache.org/jira/browse/DRILL-8132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8132: Affects Version/s: 1.20.1 > Improvement of RPC > -- > > Key: DRILL-8132 > URL: https://issues.apache.org/jira/browse/DRILL-8132 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - RPC >Affects Versions: 1.20.1 >Reporter: wtf >Assignee: wtf >Priority: Minor > > # Separate EventLoopGroup between dataserver and control client/server, as > the node which is busy on receiving data from different nodes may occupy all > EventLoopGroup threads, will block the control rpc message, e.g. fragment > transfer. > # Change the default threads of EventLoopGroup to 8(current is 10), as it > can improve performance if the number is power of two based on > PowerOfTwoEventExecutorChooser of Netty. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8125) jdbc postgresql & null JSONB fields
[
https://issues.apache.org/jira/browse/DRILL-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton updated DRILL-8125:
Affects Version/s: 1.20.1
> jdbc postgresql & null JSONB fields
> ---
>
> Key: DRILL-8125
> URL: https://issues.apache.org/jira/browse/DRILL-8125
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - JDBC
>Affects Versions: 1.20.1
>Reporter: Matteo Redaelli
>Priority: Minor
>
> Using streamline, psql, sqlline via jdbc/postgres I can query a postgres table
> {noformat}
> select instance_id, tags from aws_prd.aws_ec2_instance limit 1;
> instance_id i-0xxx
> tags {"Name": "talend-engine-01", ...}{noformat}
> {noformat}
> select instance_id, tags -> 'Name' from aws_dm_prd.aws_ec2_instance limit 1;
>
> instance_id i-0xxx
> ?column? "talend-engine-01"
> {noformat}
>
> With drill command line (drill-embeeded) I get null value for "tags" fields
> {noformat}
> apache drill> select instance_id, tags from
> steampipe.aws_dm_prd.aws_ec2_instance limit 1;
> instance_id i-0xxx
> tags null{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (DRILL-8113) Support building with a JDK 8 target using newer JDKs
[
https://issues.apache.org/jira/browse/DRILL-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton closed DRILL-8113.
---
Resolution: Fixed
> Support building with a JDK 8 target using newer JDKs
> -
>
> Key: DRILL-8113
> URL: https://issues.apache.org/jira/browse/DRILL-8113
> Project: Apache Drill
> Issue Type: Improvement
> Components: Tools, Build Test
>Affects Versions: 1.19.0
>Reporter: James Turton
>Assignee: James Turton
>Priority: Trivial
> Fix For: 1.20.2
>
>
> Currently, adding
>
> {code:java}
> 8{code}
>
> to pom.xml in order to build Drill for JDK 8 under JDK 11 will produce build
> errors relating to the package {{{}sun.security.jgss{}}}. This should be
> rectified.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8117) Clean up deprecated Apache code in Drill
[ https://issues.apache.org/jira/browse/DRILL-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8117: Affects Version/s: 1.20.1 > Clean up deprecated Apache code in Drill > > > Key: DRILL-8117 > URL: https://issues.apache.org/jira/browse/DRILL-8117 > Project: Apache Drill > Issue Type: Improvement >Affects Versions: 1.20.1 >Reporter: Jingchuan Hu >Priority: Major > Fix For: 2.0.0 > > > Clean up and upgrade deprecated Apache code like: > Class PathChildrenCache in Class ZookeeperClient and Class StringEscapeUtils > in Class PlanStringBuilder > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8117) Clean up deprecated Apache code in Drill
[ https://issues.apache.org/jira/browse/DRILL-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8117: Fix Version/s: 2.0.0 > Clean up deprecated Apache code in Drill > > > Key: DRILL-8117 > URL: https://issues.apache.org/jira/browse/DRILL-8117 > Project: Apache Drill > Issue Type: Improvement >Reporter: Jingchuan Hu >Priority: Major > Fix For: 2.0.0 > > > Clean up and upgrade deprecated Apache code like: > Class PathChildrenCache in Class ZookeeperClient and Class StringEscapeUtils > in Class PlanStringBuilder > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8106) format-excel does not handle missing cells properly
[ https://issues.apache.org/jira/browse/DRILL-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8106: Fix Version/s: 1.20.0 > format-excel does not handle missing cells properly > --- > > Key: DRILL-8106 > URL: https://issues.apache.org/jira/browse/DRILL-8106 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - Data Types >Reporter: PJ Fanning >Priority: Major > Fix For: 1.20.0 > > > ExcelBatchReader uses cellIterator assuming that this will return cells for > all columns - but this is not how that code works - the iterator only returns > non-empty cells. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8106) format-excel does not handle missing cells properly
[ https://issues.apache.org/jira/browse/DRILL-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8106: Affects Version/s: 1.19.0 > format-excel does not handle missing cells properly > --- > > Key: DRILL-8106 > URL: https://issues.apache.org/jira/browse/DRILL-8106 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - Data Types >Affects Versions: 1.19.0 >Reporter: PJ Fanning >Priority: Major > Fix For: 1.20.0 > > > ExcelBatchReader uses cellIterator assuming that this will return cells for > all columns - but this is not how that code works - the iterator only returns > non-empty cells. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8106) format-excel does not handle missing cells properly
[ https://issues.apache.org/jira/browse/DRILL-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8106. --- Assignee: PJ Fanning Resolution: Fixed > format-excel does not handle missing cells properly > --- > > Key: DRILL-8106 > URL: https://issues.apache.org/jira/browse/DRILL-8106 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - Data Types >Affects Versions: 1.19.0 >Reporter: PJ Fanning >Assignee: PJ Fanning >Priority: Major > Fix For: 1.20.0 > > > ExcelBatchReader uses cellIterator assuming that this will return cells for > all columns - but this is not how that code works - the iterator only returns > non-empty cells. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DRILL-8256) Fix unit tests of Kerberos auth in RPC
[ https://issues.apache.org/jira/browse/DRILL-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565301#comment-17565301 ] ASF GitHub Bot commented on DRILL-8256: --- jnturton commented on PR #2592: URL: https://github.com/apache/drill/pull/2592#issuecomment-1181372678 Weird, the TestBitBitKerberos class isn't being run even though I've removed the @Ignore from it. Yet there's another class in the same package called TestBitRpc which _is_ run. @vdiravka, any idea why this is happening? Is it because I converted TestBitBitKerberos to a ClusterTest? > Fix unit tests of Kerberos auth in RPC > --- > > Key: DRILL-8256 > URL: https://issues.apache.org/jira/browse/DRILL-8256 > Project: Apache Drill > Issue Type: Bug > Components: Security >Affects Versions: 1.20.1 >Reporter: James Turton >Assignee: James Turton >Priority: Minor > Fix For: 1.20.2 > > > Minor bugs in some unit tests in org.apache.drill.exec.rpc.user.security have > meant that they have been disabled historically to prevent causing CI > failures. -- This message was sent by Atlassian Jira (v8.20.10#820010)
