[
https://issues.apache.org/jira/browse/LUCENE-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652940#action_12652940
]
robert engels commented on LUCENE-1473:
---------------------------------------
Jason, you are only partially correct.
SOLR has XML definitions for updates/commits/deletes. It also supports string
based queries. It also supports using XML for queries if you provide a handler,
but the string syntax is simpler.
As for the serialization performance, you are mistaken.
For things like searches, the parsing time is extremely minor compared with the
search time, so this additional overhead would be a fraction of the cost.
When returning results sets, using XML can make a huge difference, as the
overhead to paid on every item. Even still with modern XML processors, the
search time is still going to be the overriding performance factor by a huge
margin. Typically "paged" results are also used, so again, the XML parsing
compared to the network overhead, is going to be minor.
Still, if it is only for temporary serialization, binary works best - as long
as it is Java to Java.
We have a search server that uses Java serialization for the message passing,
including the results. It can be done without any changes to Lucene - again the
overriding performance factor is the search itself (unless the queries returns
100k + documents and all are being returned - then the Java serialization time
can be more than the search itself...
> Implement Externalizable in main top level searcher classes
> -----------------------------------------------------------
>
> Key: LUCENE-1473
> URL: https://issues.apache.org/jira/browse/LUCENE-1473
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.4
> Reporter: Jason Rutherglen
> Priority: Minor
> Attachments: LUCENE-1473.patch
>
>
> To maintain serialization compatibility between Lucene versions, major
> classes can implement Externalizable. This will make Serialization faster
> due to no reflection required and maintain backwards compatibility.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
