[
https://issues.apache.org/jira/browse/AVRO-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J Chouraria updated AVRO-682:
-----------------------------------
Attachment: avro.metadata.datafile.r2.diff
Alternative patch that gives a mere list of keys to use. I guess it'd come with
some reserved Avro DF keys also, which prevents me from writing a size or
element-compare test case for the same method (as I do not know how many/what
all reserved keys get added -- I think codec is one).
But the list should be usable, I guess. People could ignore "avro." stuff. Or
should we filter those out?
> Expose the DataFile's metadata entirely
> ---------------------------------------
>
> Key: AVRO-682
> URL: https://issues.apache.org/jira/browse/AVRO-682
> Project: Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.4.1
> Environment: Linux, Java 1.6
> Reporter: Harsh J Chouraria
> Assignee: Harsh J Chouraria
> Priority: Minor
> Fix For: 1.5.0
>
> Attachments: avro.metadata.datafile.r1.diff,
> avro.metadata.datafile.r1.diff, avro.metadata.datafile.r2.diff
>
> Original Estimate: 0.02h
> Remaining Estimate: 0.02h
>
> Right now, the DataFileReader (DataFileStream actually) only allows one to
> query the meta data of a file by issuing a key. A user who does not know what
> metadata may be stored in the file, has no way to find out by getting a
> list/map of all there is. Perhaps we should provide a way for the user to
> retrieve global metadata info to query it back for values.
> Attached a patch (initial) that simply exposes the HashMap that contains the
> metadata after initialization of the data file reader.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
