[jira] [Commented] (DRILL-7875) NPE in Splunk Queries

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DRILL-7875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296719#comment-17296719 ] 

ASF GitHub Bot commented on DRILL-7875:
---------------------------------------

cgivre commented on pull request #2184:
URL: https://github.com/apache/drill/pull/2184#issuecomment-792188267


   @vvysotskyi I fixed this PR to use the latest changes from your s3 fix.  Now it just addresses the NPE from Splunk indexes w/o timestamps.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> NPE in Splunk Queries
> ---------------------
>
>                 Key: DRILL-7875
>                 URL: https://issues.apache.org/jira/browse/DRILL-7875
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Storage - Other
>    Affects Versions: 1.19.0
>            Reporter: Charles Givre
>            Assignee: Charles Givre
>            Priority: Major
>             Fix For: 1.19.0
>
>
> In Splunk queries, if one of the fields containing an INT or TIMESTAMP is null, the BatchReader will crash.  This fix simply adds a check to verify that there is data and if not, set the reader to null.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)