Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
The format format in which bytes are stored in BytesRef and the javabin string format are both the same. We don't need to convert the string/text fields from BytesRef to String and back to UTF8
Now a String/Text field is read and written out as follows
luceneindex(UTF8 bytes) --> UTF16 (char[]) --> new String() a copy of UTF16 char[] --> UTF8bytes(javabin format)
This does not add a new type to javabin. It's encoded as String in the serialized data. When it is deserialized, you get a String back
Attachments
Attachments
Issue Links
- is a parent of
-
SOLR-14013 javabin performance regressions
-
- Closed
-
- is related to
-
SOLR-12983 JavabinLoader should avoid creating String Objects and create UTF8CharSequence fields from byte[]
-
- Closed
-
-
SOLR-12924 Optimize JavabinCodec to use byte[] backed CharSequence instead of String
-
- Closed
-