[jira] [Commented] (DRILL-8377) While accessing a Uppercase databasename in Drill its getting converted to lower case and then throwing error cant access database
[
https://issues.apache.org/jira/browse/DRILL-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17652316#comment-17652316
]
SHUBHAM KUMAR commented on DRILL-8377:
--
Can you please help with any configuration which helps to retrive the database
name as it is. it should not convert it to lower case
> While accessing a Uppercase databasename in Drill its getting converted to
> lower case and then throwing error cant access database
> --
>
> Key: DRILL-8377
> URL: https://issues.apache.org/jira/browse/DRILL-8377
> Project: Apache Drill
> Issue Type: Bug
>Reporter: SHUBHAM KUMAR
>Priority: Major
>
> While accessing a Uppercase databasename in Drill its getting converted to
> lower case and then throwing error cant access database
>
> Command failed with error 13 (Unauthorized): 'not authorized on test-database
> to execute command.
> org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
> MongoCommandException: Command failed with error 13 (Unauthorized): 'not
> authorized on test-database to execute command \{ count: "PaymentsDev",
> query: {}, $db: "test-database", $clusterTime:
>
> Actual Database Name: Test-Database
> Drill converting it as: test-database
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8377) While accessing a Uppercase databasename in Drill its getting converted to lower case and then throwing error cant access database
[
https://issues.apache.org/jira/browse/DRILL-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SHUBHAM KUMAR updated DRILL-8377:
-
Description:
While accessing a Uppercase databasename in Drill its getting converted to
lower case and then throwing error cant access database
Command failed with error 13 (Unauthorized): 'not authorized on test-database
to execute command.
org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
MongoCommandException: Command failed with error 13 (Unauthorized): 'not
authorized on test-database to execute command \{ count: "PaymentsDev", query:
{}, $db: "test-database", $clusterTime:
Actual Database Name: Test-Database
Drill converting it as: test-database
was:
While accessing a Uppercase databasename in Drill its getting converted to
lower case and then throwing error cant access database
Command failed with error 13 (Unauthorized): 'not authorized on qa-omniprofile
to execute command.
org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
MongoCommandException: Command failed with error 13 (Unauthorized): 'not
authorized on qa-omniprofile to execute command \{ count: "PaymentsDev", query:
{}, $db: "qa-omniprofile", $clusterTime:
> While accessing a Uppercase databasename in Drill its getting converted to
> lower case and then throwing error cant access database
> --
>
> Key: DRILL-8377
> URL: https://issues.apache.org/jira/browse/DRILL-8377
> Project: Apache Drill
> Issue Type: Bug
>Reporter: SHUBHAM KUMAR
>Priority: Major
>
> While accessing a Uppercase databasename in Drill its getting converted to
> lower case and then throwing error cant access database
>
> Command failed with error 13 (Unauthorized): 'not authorized on test-database
> to execute command.
> org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
> MongoCommandException: Command failed with error 13 (Unauthorized): 'not
> authorized on test-database to execute command \{ count: "PaymentsDev",
> query: {}, $db: "test-database", $clusterTime:
>
> Actual Database Name: Test-Database
> Drill converting it as: test-database
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8377) While accessing a Uppercase databasename in Drill its getting converted to lower case and then throwing error cant access database
[
https://issues.apache.org/jira/browse/DRILL-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SHUBHAM KUMAR updated DRILL-8377:
-
Description:
While accessing a Uppercase databasename in Drill its getting converted to
lower case and then throwing error cant access database
Command failed with error 13 (Unauthorized): 'not authorized on qa-omniprofile
to execute command.
org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
MongoCommandException: Command failed with error 13 (Unauthorized): 'not
authorized on qa-omniprofile to execute command \{ count: "PaymentsDev", query:
{}, $db: "qa-omniprofile", $clusterTime:
was:
Command failed with error 13 (Unauthorized): 'not authorized on qa-omniprofile
to execute command.
org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
MongoCommandException: Command failed with error 13 (Unauthorized): 'not
authorized on qa-omniprofile to execute command \{ count: "PaymentsDev", query:
{}, $db: "qa-omniprofile", $clusterTime:
> While accessing a Uppercase databasename in Drill its getting converted to
> lower case and then throwing error cant access database
> --
>
> Key: DRILL-8377
> URL: https://issues.apache.org/jira/browse/DRILL-8377
> Project: Apache Drill
> Issue Type: Bug
>Reporter: SHUBHAM KUMAR
>Priority: Major
>
> While accessing a Uppercase databasename in Drill its getting converted to
> lower case and then throwing error cant access database
>
> Command failed with error 13 (Unauthorized): 'not authorized on
> qa-omniprofile to execute command.
> org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
> MongoCommandException: Command failed with error 13 (Unauthorized): 'not
> authorized on qa-omniprofile to execute command \{ count: "PaymentsDev",
> query: {}, $db: "qa-omniprofile", $clusterTime:
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8377) While accessing a Uppercase databasename in Drill its getting converted to lower case and then throwing error cant access database
[
https://issues.apache.org/jira/browse/DRILL-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SHUBHAM KUMAR updated DRILL-8377:
-
Description:
Command failed with error 13 (Unauthorized): 'not authorized on qa-omniprofile
to execute command.
org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
MongoCommandException: Command failed with error 13 (Unauthorized): 'not
authorized on qa-omniprofile to execute command \{ count: "PaymentsDev", query:
{}, $db: "qa-omniprofile", $clusterTime:
was:
Command failed with error 13 (Unauthorized): 'not authorized on qa-omniprofile
to execute command.
> While accessing a Uppercase databasename in Drill its getting converted to
> lower case and then throwing error cant access database
> --
>
> Key: DRILL-8377
> URL: https://issues.apache.org/jira/browse/DRILL-8377
> Project: Apache Drill
> Issue Type: Bug
>Reporter: SHUBHAM KUMAR
>Priority: Major
>
> Command failed with error 13 (Unauthorized): 'not authorized on
> qa-omniprofile to execute command.
> org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
> MongoCommandException: Command failed with error 13 (Unauthorized): 'not
> authorized on qa-omniprofile to execute command \{ count: "PaymentsDev",
> query: {}, $db: "qa-omniprofile", $clusterTime:
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8377) While accessing a Uppercase databasename in Drill its getting converted to lower case and then throwing error cant access database
[ https://issues.apache.org/jira/browse/DRILL-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SHUBHAM KUMAR updated DRILL-8377: - Summary: While accessing a Uppercase databasename in Drill its getting converted to lower case and then throwing error cant access database (was: Command failed with error 13 (Unauthorized): 'not authorized on qa-omniprofile to execute command) > While accessing a Uppercase databasename in Drill its getting converted to > lower case and then throwing error cant access database > -- > > Key: DRILL-8377 > URL: https://issues.apache.org/jira/browse/DRILL-8377 > Project: Apache Drill > Issue Type: Bug >Reporter: SHUBHAM KUMAR >Priority: Major > > Command failed with error 13 (Unauthorized): 'not authorized on > qa-omniprofile to execute command. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8377) Command failed with error 13 (Unauthorized): 'not authorized on qa-omniprofile to execute command
[ https://issues.apache.org/jira/browse/DRILL-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SHUBHAM KUMAR updated DRILL-8377: - Description: Command failed with error 13 (Unauthorized): 'not authorized on qa-omniprofile to execute command. > Command failed with error 13 (Unauthorized): 'not authorized on > qa-omniprofile to execute command > - > > Key: DRILL-8377 > URL: https://issues.apache.org/jira/browse/DRILL-8377 > Project: Apache Drill > Issue Type: Bug >Reporter: SHUBHAM KUMAR >Priority: Major > > Command failed with error 13 (Unauthorized): 'not authorized on > qa-omniprofile to execute command. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DRILL-8377) Command failed with error 13 (Unauthorized): 'not authorized on qa-omniprofile to execute command
SHUBHAM KUMAR created DRILL-8377: Summary: Command failed with error 13 (Unauthorized): 'not authorized on qa-omniprofile to execute command Key: DRILL-8377 URL: https://issues.apache.org/jira/browse/DRILL-8377 Project: Apache Drill Issue Type: Bug Reporter: SHUBHAM KUMAR -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8302) tidy up some char conversions
[
https://issues.apache.org/jira/browse/DRILL-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton closed DRILL-8302.
---
Resolution: Fixed
> tidy up some char conversions
> -
>
> Key: DRILL-8302
> URL: https://issues.apache.org/jira/browse/DRILL-8302
> Project: Apache Drill
> Issue Type: Improvement
>Reporter: PJ Fanning
>Assignee: PJ Fanning
>Priority: Major
> Fix For: 1.21.0
>
>
> As part of DRILL-8301, I spotted code that could be tidied up. The aim of
> this issue is to reduce the size of DRILL-8301 without introducing changes to
> the char encodings.
> * uses of a pattern like `new String("")` - IntelliJ and other tools
> highlight this as unnecessary
> * uses of `new String(bytes, StandardCharsets.UTF_8.name())` - better to use
> `new String(bytes, StandardCharsets.UTF_8)`
> * use Base64 encodeToString instead of case where we encode to bytes and
> then do our own encoding of those bytes to a String
> * Change existing code with `Charset.forName("UTF-8")` to use
> `StandardCharsets.UTF_8`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (DRILL-8302) tidy up some char conversions
[
https://issues.apache.org/jira/browse/DRILL-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton reopened DRILL-8302:
-
Assignee: PJ Fanning
> tidy up some char conversions
> -
>
> Key: DRILL-8302
> URL: https://issues.apache.org/jira/browse/DRILL-8302
> Project: Apache Drill
> Issue Type: Improvement
>Reporter: PJ Fanning
>Assignee: PJ Fanning
>Priority: Major
> Fix For: 1.20.3
>
>
> As part of DRILL-8301, I spotted code that could be tidied up. The aim of
> this issue is to reduce the size of DRILL-8301 without introducing changes to
> the char encodings.
> * uses of a pattern like `new String("")` - IntelliJ and other tools
> highlight this as unnecessary
> * uses of `new String(bytes, StandardCharsets.UTF_8.name())` - better to use
> `new String(bytes, StandardCharsets.UTF_8)`
> * use Base64 encodeToString instead of case where we encode to bytes and
> then do our own encoding of those bytes to a String
> * Change existing code with `Charset.forName("UTF-8")` to use
> `StandardCharsets.UTF_8`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8302) tidy up some char conversions
[
https://issues.apache.org/jira/browse/DRILL-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton updated DRILL-8302:
Fix Version/s: 1.21.0
(was: 1.20.3)
> tidy up some char conversions
> -
>
> Key: DRILL-8302
> URL: https://issues.apache.org/jira/browse/DRILL-8302
> Project: Apache Drill
> Issue Type: Improvement
>Reporter: PJ Fanning
>Assignee: PJ Fanning
>Priority: Major
> Fix For: 1.21.0
>
>
> As part of DRILL-8301, I spotted code that could be tidied up. The aim of
> this issue is to reduce the size of DRILL-8301 without introducing changes to
> the char encodings.
> * uses of a pattern like `new String("")` - IntelliJ and other tools
> highlight this as unnecessary
> * uses of `new String(bytes, StandardCharsets.UTF_8.name())` - better to use
> `new String(bytes, StandardCharsets.UTF_8)`
> * use Base64 encodeToString instead of case where we encode to bytes and
> then do our own encoding of those bytes to a String
> * Change existing code with `Charset.forName("UTF-8")` to use
> `StandardCharsets.UTF_8`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8299) HashMap key type mismatch in MetadataContext
[
https://issues.apache.org/jira/browse/DRILL-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton updated DRILL-8299:
Fix Version/s: 1.21.0
(was: 1.20.3)
> HashMap key type mismatch in MetadataContext
>
>
> Key: DRILL-8299
> URL: https://issues.apache.org/jira/browse/DRILL-8299
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.20.2
>Reporter: PJ Fanning
>Assignee: James Turton
>Priority: Minor
> Fix For: 1.21.0
>
>
> The dirModifCheckMap used in this lookup is keyed using a HDFS Path instance,
> not a string, so this code is not going to work:
> {code:java}
> public boolean getStatus(String dir) {
> if (dirModifCheckMap.containsKey(dir)) {
> return dirModifCheckMap.get(dir);
> }
> return false;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (DRILL-8299) HashMap key type mismatch in MetadataContext
[
https://issues.apache.org/jira/browse/DRILL-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton reopened DRILL-8299:
-
> HashMap key type mismatch in MetadataContext
>
>
> Key: DRILL-8299
> URL: https://issues.apache.org/jira/browse/DRILL-8299
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.20.2
>Reporter: PJ Fanning
>Assignee: James Turton
>Priority: Minor
> Fix For: 1.20.3
>
>
> The dirModifCheckMap used in this lookup is keyed using a HDFS Path instance,
> not a string, so this code is not going to work:
> {code:java}
> public boolean getStatus(String dir) {
> if (dirModifCheckMap.containsKey(dir)) {
> return dirModifCheckMap.get(dir);
> }
> return false;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (DRILL-8370) Upgrade splunk-sdk-java to 1.9.3
[
https://issues.apache.org/jira/browse/DRILL-8370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton closed DRILL-8370.
---
Resolution: Fixed
> Upgrade splunk-sdk-java to 1.9.3
>
>
> Key: DRILL-8370
> URL: https://issues.apache.org/jira/browse/DRILL-8370
> Project: Apache Drill
> Issue Type: Improvement
> Components: Storage - Other
>Affects Versions: 1.20.2
>Reporter: James Turton
>Assignee: James Turton
>Priority: Minor
> Fix For: 1.21.0
>
>
> Changes in splunk-sdk-java since 1.9.1.
> {quote}
> h3. Minor Changes
> * Re-fetch logic for instancetype and version fields if not set within
> Service instance to avoid NPE (GitHub PR
> [#202|https://github.com/splunk/splunk-sdk-java/pull/202])
> * Check for local IP as alternative to _localhost_ within HostnameVerifier,
> addressing issue with certain local workflows
> * Added null check for child to handle error when no value is passed for a
> parameter in modular-inputs (Ref issue
> [#198|https://github.com/splunk/splunk-sdk-java/issues/198] & GitHub PR
> [#199|https://github.com/splunk/splunk-sdk-java/pull/199])
> h3. New Features and APIs
> {quote} *
> {quote}Added feature that allows to update ACL properties of an entity
> (GitHub PR [#196|https://github.com/splunk/splunk-sdk-java/pull/196]){quote}
>
> Also removes the execution order dependence in the Splunk unit tests created
> by their expecting a certain number of records in the _audit index. I believe
> this order dependence is behind recent, apparently random CI run failures in
> the Splunk unit tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8370) Upgrade splunk-sdk-java to 1.9.3
[
https://issues.apache.org/jira/browse/DRILL-8370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton updated DRILL-8370:
Fix Version/s: 1.21.0
(was: 1.20.3)
> Upgrade splunk-sdk-java to 1.9.3
>
>
> Key: DRILL-8370
> URL: https://issues.apache.org/jira/browse/DRILL-8370
> Project: Apache Drill
> Issue Type: Improvement
> Components: Storage - Other
>Affects Versions: 1.20.2
>Reporter: James Turton
>Assignee: James Turton
>Priority: Minor
> Fix For: 1.21.0
>
>
> Changes in splunk-sdk-java since 1.9.1.
> {quote}
> h3. Minor Changes
> * Re-fetch logic for instancetype and version fields if not set within
> Service instance to avoid NPE (GitHub PR
> [#202|https://github.com/splunk/splunk-sdk-java/pull/202])
> * Check for local IP as alternative to _localhost_ within HostnameVerifier,
> addressing issue with certain local workflows
> * Added null check for child to handle error when no value is passed for a
> parameter in modular-inputs (Ref issue
> [#198|https://github.com/splunk/splunk-sdk-java/issues/198] & GitHub PR
> [#199|https://github.com/splunk/splunk-sdk-java/pull/199])
> h3. New Features and APIs
> {quote} *
> {quote}Added feature that allows to update ACL properties of an entity
> (GitHub PR [#196|https://github.com/splunk/splunk-sdk-java/pull/196]){quote}
>
> Also removes the execution order dependence in the Splunk unit tests created
> by their expecting a certain number of records in the _audit index. I believe
> this order dependence is behind recent, apparently random CI run failures in
> the Splunk unit tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (DRILL-8366) Late release of compressor memory in the Parquet writer
[ https://issues.apache.org/jira/browse/DRILL-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8366. --- Resolution: Fixed > Late release of compressor memory in the Parquet writer > --- > > Key: DRILL-8366 > URL: https://issues.apache.org/jira/browse/DRILL-8366 > Project: Apache Drill > Issue Type: Bug > Components: Storage - Parquet >Affects Versions: 1.20.2 >Reporter: James Turton >Assignee: James Turton >Priority: Minor > Fix For: 1.20.3 > > > The Parquet writer waits until the end of the entire write before releasing > its compression codec factory. The factory in turn releases compressors which > release direct memory buffers used during compression. This deferred release > leads a build up of direct memory use and can cause large write jobs to fail. > The Parquet writer can instead release the abovementioned each time that a > file/row group is flushed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8299) HashMap key type mismatch in MetadataContext
[
https://issues.apache.org/jira/browse/DRILL-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton closed DRILL-8299.
---
> HashMap key type mismatch in MetadataContext
>
>
> Key: DRILL-8299
> URL: https://issues.apache.org/jira/browse/DRILL-8299
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.20.2
>Reporter: PJ Fanning
>Assignee: James Turton
>Priority: Minor
> Fix For: 1.20.3
>
>
> The dirModifCheckMap used in this lookup is keyed using a HDFS Path instance,
> not a string, so this code is not going to work:
> {code:java}
> public boolean getStatus(String dir) {
> if (dirModifCheckMap.containsKey(dir)) {
> return dirModifCheckMap.get(dir);
> }
> return false;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8336) HTTP UDFs do not correctly handle results rooted in an array
[ https://issues.apache.org/jira/browse/DRILL-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8336: Fix Version/s: 1.21.0 (was: 1.20.3) > HTTP UDFs do not correctly handle results rooted in an array > > > Key: DRILL-8336 > URL: https://issues.apache.org/jira/browse/DRILL-8336 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - HTTP >Affects Versions: 1.20.2 >Reporter: James Turton >Priority: Minor > Fix For: 1.21.0 > > > When the HTTP udfs http_get or http_request are used against an endpoint that > returns JSON data that is rooted with an array (or line-delimited object > sequence) then they return consecutive objects from that array with each > invocation until the end is reached, after which the next invocation fails > with an error. This can be reproduced by having a web server serve Drill's > donuts.json. > In addition, each invocation of these UDFs leaks a single file descriptor. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (DRILL-8299) HashMap key type mismatch in MetadataContext
[
https://issues.apache.org/jira/browse/DRILL-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton resolved DRILL-8299.
-
Resolution: Fixed
> HashMap key type mismatch in MetadataContext
>
>
> Key: DRILL-8299
> URL: https://issues.apache.org/jira/browse/DRILL-8299
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.20.2
>Reporter: PJ Fanning
>Assignee: James Turton
>Priority: Minor
> Fix For: 1.20.3
>
>
> The dirModifCheckMap used in this lookup is keyed using a HDFS Path instance,
> not a string, so this code is not going to work:
> {code:java}
> public boolean getStatus(String dir) {
> if (dirModifCheckMap.containsKey(dir)) {
> return dirModifCheckMap.get(dir);
> }
> return false;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (DRILL-8365) HTTP Plugin Places Parameters in Wrong Place
[ https://issues.apache.org/jira/browse/DRILL-8365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton closed DRILL-8365. --- > HTTP Plugin Places Parameters in Wrong Place > > > Key: DRILL-8365 > URL: https://issues.apache.org/jira/browse/DRILL-8365 > Project: Apache Drill > Issue Type: Bug > Components: Storage - HTTP >Affects Versions: 1.20.2 >Reporter: Charles Givre >Assignee: Charles Givre >Priority: Major > Fix For: 1.20.3 > > > When the requireTail option is set to true, and pagination is enabled, the > HTTP plugin puts the required parameters in the wrong place in the URL. This > PR fixes that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DRILL-8296) Possible type mismatch bug in SplunkBatchReader
[
https://issues.apache.org/jira/browse/DRILL-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton closed DRILL-8296.
---
> Possible type mismatch bug in SplunkBatchReader
> ---
>
> Key: DRILL-8296
> URL: https://issues.apache.org/jira/browse/DRILL-8296
> Project: Apache Drill
> Issue Type: Improvement
> Components: splunk
>Affects Versions: 1.20.2
>Reporter: PJ Fanning
>Assignee: James Turton
>Priority: Minor
> Fix For: 1.20.3
>
>
> {code:java}
> if (path.nameEquals("**")) {
> return true;
> } else {
> return specialFields.contains(path.getAsNamePart());
> }
> {code}
> LGTM and IntelliJ both say that NamePart type does not match the type stored
> in specialFields collection.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
