orc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From naveen mahadevuni <nmahadev...@gmail.com>
Subject Re: Sub-classing implementation classes(e.g., ReaderImpl)
Date Wed, 29 May 2019 18:13:45 GMT
Thanks Deepak, Serialized file tail helps.

On Wed, May 29, 2019 at 8:07 PM Deepak Majeti <majeti.deepak@gmail.com>
wrote:

> Hi Naveen,
>
> The Impl classes, in general, are internal implementations and should not
> have to be part of the public API.
>
> Your requirement can currently be supported by saving the serialized
> metadata locally and then passing the serialized metadata to the Reader as
> part of the options. See ReaderOptions::setSerializedFileTail()
>
> This will then invoke reads from cloud store only for the data.
>
>
> On Wed, May 29, 2019 at 5:42 PM naveen mahadevuni <nmahadevuni@gmail.com>
> wrote:
>
> > Hi,
> >
> > We are using ORC C++ API. We would like to be able to sub-class the ORC
> > implementation classes such as ReaderImpl, StatisticsImpl,
> > StripeInformationImpl... The reason being, when ORC files are stored on a
> > cloud store such as S3, we would like to have the metadata/statistics
> > stored on a file on local disk and create wrapper implementation classes
> > which read metadata/statistics from locally stored file and delegates
> only
> > the data stream reads to the cloud store.
> >
> > Will there be any problems if these implementation classes are published?
> >
> > Thanks,
> > Naveen
> >
>
>
> --
> regards,
> Deepak Majeti
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message