Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

BinCasSerializer needs Source Typesystem #2

Open
GoogleCodeExporter opened this issue Apr 13, 2015 · 1 comment
Open

BinCasSerializer needs Source Typesystem #2

GoogleCodeExporter opened this issue Apr 13, 2015 · 1 comment
Labels
bug

Comments

@GoogleCodeExporter
Copy link 

To be able to deal with different Typesystems, BinCasWritable needs to store 
the Typesystem alongside the data.

This can be either as header to each document (highly renundant) or as a 
seperate file alongside each sequencefile on hdfs.

Original issue reported on code.google.com by [email protected] on 13 Sep 2013 at 4:50
@GoogleCodeExporter
Copy link
Author 

Fixed by introducing BinCasWithTypesystemWritable, which serializes a 
compressed Typesystem with each CAS.

Those files are considerable larger than XMI compressed with Snappy. 

The user can always choose to use the old format by setting 
job.setOutPutValueClass(CASWritable.class)

TODO: store the typesystem seperately, this will be the optimal solution.

Original comment by [email protected] on 30 Sep 2013 at 4:27

  • Added labels: Priority-Low
  • Removed labels: Priority-High

@reckart reckart added bug and removed Priority-Low labels Jun 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@reckart @GoogleCodeExporter