[teiid-issues] [JBoss JIRA] (TEIID-5936) create an s3 file source

[Steven Hawkins (Jira)]

     [ https://issues.redhat.com/browse/TEIID-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-5936:
----------------------------------
    Description: 
The existing s3 support is implemented as a translator / ws source combo.  We instead need this to be just a source to allow for translators to utilize it (excel, parquet, avro).

As an alternative to our existing support we should evaluate utilizing the sdk rather than providing our own processing logic.  More than likely this will be a quicker path to things like s3 select support.  However ceph seems to lag in s3 support (see TEIID-5935 and no s3 select support) so we'd have to compensate, make the metadata and/or the capabilities specific to the connection type.

  was:As an alternative to our existing support we should evaluate utilizing the sdk rather than providing our own processing logic.  More than likely this will be a quicker path to things like s3 select support.  However ceph seems to lag in s3 support (see TEIID-5935 and no s3 select support) so we'd have to compensate, make the metadata and/or the capabilities specific to the connection type.

        Summary: create an s3 file source   (was: evaluate aws sdk for java for s3 support)


> create an s3 file source 
> -------------------------
>
>                 Key: TEIID-5936
>                 URL: https://issues.redhat.com/browse/TEIID-5936
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Misc. Connectors
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>            Priority: Major
>             Fix For: 15.0
>
>
> The existing s3 support is implemented as a translator / ws source combo.  We instead need this to be just a source to allow for translators to utilize it (excel, parquet, avro).
> As an alternative to our existing support we should evaluate utilizing the sdk rather than providing our own processing logic.  More than likely this will be a quicker path to things like s3 select support.  However ceph seems to lag in s3 support (see TEIID-5935 and no s3 select support) so we'd have to compensate, make the metadata and/or the capabilities specific to the connection type.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)