[
https://issues.apache.org/jira/browse/UIMA-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018033#comment-15018033
]
Richard Eckart de Castilho edited comment on UIMA-4685 at 11/20/15 1:42 PM:
----------------------------------------------------------------------------
DKPro Core BinaryCasWriter currently uses ".bin" irrespective of the format.
The DKPro BinaryCasReader automatically detects the format from the stream and
uses the correct deserialization internally.
It supports different formats:
* S - CASSerializer
* S+ - CASCompleteSerializer
* 0 - serializeCAS(...)
* 4 - serializeWithCompression(cas, stream)
* 6 - serializeWithCompression(cas, stream, ts)
* 6+ - 6 with embedded type system (this is a special DKPro Core thing, but
would be nice to have in UIMA actually)
was (Author: rec):
DKPro Core BinaryCasWriter currently uses ".bin" irrespective of the format.
The DKPro BinaryCasReader automatically detects the format from the stream and
uses the correct deserialization internally.
> Support different CAS serializations in CAS Editor
> --------------------------------------------------
>
> Key: UIMA-4685
> URL: https://issues.apache.org/jira/browse/UIMA-4685
> Project: UIMA
> Issue Type: New Feature
> Components: CasEditor
> Affects Versions: 2.8.1SDK
> Reporter: Peter Klügl
> Attachments: caseditor.csv
>
>
> Support different CAS serializations in CAS Editor. Some recent profiling
> revealed that, when opening a 35MB xmiCAS, the CAS Editor spends about 70% of
> its time for deserializing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
