you can use an approach like HADDOP's TFile
https://issues.apache.org/jira/secure/attachment/12396286/TFile%20Specification%2020081217.pdf
basically they store compressed chunks in a file, and at the end of the
file (hence T(ail)File) they store come kind of a sparse index to
the chunks.
Comment #8 on issue 298 by cjdo...@gmail.com: protobuf jar's manifest
should include OSGi metadata
http://code.google.com/p/protobuf/issues/detail?id=298
The advantage of comment #7's approach is that OSGi vs. Maven version
number syntax is automatically handled by the plugin. I strongly
Comment #1 on issue 352 by ryandani...@gmail.com: ENH: Add configure option
to disable Java / Python / C++
http://code.google.com/p/protobuf/issues/detail?id=352
I am also looking for this option. This adds significant time to my build,
so it'd be nice to remove Java/Python from the build.
Hi all. I've just came across GPB and I found it quite interesting.
I'm a newbie, so I went through the CPP tutorial they have given and
tried out the examples.
https://developers.google.com/protocol-buffers/docs/cpptutorial
The example basically consists of these files: addressbook.proto,
Hey all,
I've been doing tests with the protoBuff and protoStuff APIs to see
whats a better fit for our problem. We are going to have multiple
clients- wich may have multiple versions of objects- accessing
serialized object data in a chache. We have been looking into
protoBuff/stuff as a
Thank you all.
I think TFile is very similar to what I am trying to do.
One issue of TFile is that it stores all meta and indices in its tail
which in turn means that if the writing process suddenly crashes for
some reason (e.g. hardware issue or something not related to our
process) then file
