[ 
https://issues.apache.org/jira/browse/HADOOP-17945?focusedWorklogId=657295&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-657295
 ]

ASF GitHub Bot logged work on HADOOP-17945:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 29/Sep/21 14:53
            Start Date: 29/Sep/21 14:53
    Worklog Time Spent: 10m 
      Work Description: steveloughran opened a new pull request #3501:
URL: https://github.com/apache/hadoop/pull/3501


    
   
   (lifted from MAPREDUCE-7341)
   
   
   ### How was this patch tested?
   
   * updated tests
   * rerunning s3a committer suite
   * In MAPREDUCE-7341; testing against azure abfs too
   
   
   
   - [X] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [X] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   
   


-- 
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.

To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org

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


Issue Time Tracking
-------------------

            Worklog Id:     (was: 657295)
    Remaining Estimate: 0h
            Time Spent: 10m

> JsonSerialization raises EOFException reading JSON data stored on google GCS
> ----------------------------------------------------------------------------
>
>                 Key: HADOOP-17945
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17945
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 3.3.1
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The JsonSerialization<> load code doesn't work on gcs as it uses 
> "stream.available()" to fail with a meaningful message if the stream is empty.
> But that method is meant to say how much data is available without blocking, 
> something we actually get wrong ourselves. Google GCS team didn't get it 
> wrong, so on a read(), if there's no local buffer, an EOFException is raised



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

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to