-
Notifications
You must be signed in to change notification settings - Fork 6
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.
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
New serialization method from uima 2.4.2 broke CAS visualization in cse-gui #19
Comments
I agree, we can follow your suggestion, let me fix that tonight. On Wed, Oct 16, 2013 at 3:09 PM, Zi Yang [email protected] wrote:
|
Thank, @elmer-garduno . Do we also need an additional field in the cas_str table to indicate what serialization method is used, maybe? |
I think the deserializer has some heuristics to achieve that, let me find On Wed, Oct 16, 2013 at 3:30 PM, Zi Yang [email protected] wrote:
|
Some header trick maybe? On Wed 16 Oct 2013 04:46:37 PM EDT, Elmer Garduño wrote:
|
Due to the new serialization method, the cas blob is no longer accessible by non-UIMA SDK based program, e.g. the new CSE GUI, which used to gunzip the blob and treat it as an XMI string and do the parsing. I don't know if the new 2.4.2 still has the old serialization method available in the package, but what I might suggest for now is to have both serialization methods available for uima-ecd. A common use example is that we use the new serialization method for intermediate data persistence, and directly store the compressed XMI string generated from the last cas in the pipeline. We can have two different "persistence-provider"s or "phase"s, and users are responsible to use the right one for each phase.
The text was updated successfully, but these errors were encountered: