SinghAsDev commented on issue #859:
URL: https://github.com/apache/iceberg/issues/859#issuecomment-906802774


   I think that makes sense. The readers will then return just the file names?
   Just curious, what type of metadata would one want to store for each file?
   Would metadata be a specific type or like a dictionary?
   
   Is the discussion on Apache slack? I could not find the thread with a few
   keyword searches like blob and unstructured data 😀.
   
   On Thu, Aug 26, 2021 at 3:52 PM Ryan Blue ***@***.***> wrote:
   
   > We talked about this recently in Slack. An alternative that I like is
   > adding a BLOB type to the spec that is backed by a file. Then each
   > unstructured file is represented by a row in a table that can contain
   > metadata, and isn't just a file reference in an Iceberg manifest file.
   >
   > I think using a BLOB type is a simpler path to managing unstructured data
   > collections and end up delivering more features.
   >
   > —
   > You are receiving this because you commented.
   > Reply to this email directly, view it on GitHub
   > <https://github.com/apache/iceberg/issues/859#issuecomment-906794720>, or
   > unsubscribe
   > 
<https://github.com/notifications/unsubscribe-auth/ABFQCZPQMGUKSPZUM4GFFODT63ARVANCNFSM4LRCNE2Q>
   > .
   > Triage notifications on the go with GitHub Mobile for iOS
   > 
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
   > or Android
   > 
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
   >
   >
   -- 
   - Ashish
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to