[ 
https://issues.apache.org/jira/browse/HIVE-22499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gopal Vijayaraghavan updated HIVE-22499:
----------------------------------------
    Description: 
ORC-570 is an ABI change to the way getFileSystem() by adding an another 
exception to the implementation.

To accept and use that change requires waiting for an ORC release, while this 
patch serves the same purpose though falls back for a retry for 
FileSystem.get() in case the supplier fails at runtime.

Also as a side-note, the FS.get() call is always used in the cases where the 
file is not being read from a cache such as EncodedOrcFile (so the upstream API 
change might be overkill).

  was:
ORC-570 is an ABI change to the way getFileSystem() by adding an another 
exception to the implementation.

To accept and use that change requires waiting for an ORC release, while this 
patch serves the same purpose though falls back for a retry for 
FileSystem.get() in case the supplier fails at runtime.


> LLAP: Add an EncodedReaderOptions to extend ORC impl for options
> ----------------------------------------------------------------
>
>                 Key: HIVE-22499
>                 URL: https://issues.apache.org/jira/browse/HIVE-22499
>             Project: Hive
>          Issue Type: Bug
>          Components: llap, ORC
>            Reporter: Gopal Vijayaraghavan
>            Priority: Major
>         Attachments: HIVE-22499.WIP.patch
>
>
> ORC-570 is an ABI change to the way getFileSystem() by adding an another 
> exception to the implementation.
> To accept and use that change requires waiting for an ORC release, while this 
> patch serves the same purpose though falls back for a retry for 
> FileSystem.get() in case the supplier fails at runtime.
> Also as a side-note, the FS.get() call is always used in the cases where the 
> file is not being read from a cache such as EncodedOrcFile (so the upstream 
> API change might be overkill).



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

Reply via email to