[
https://issues.apache.org/jira/browse/SOLR-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474337
]
Hoss Man commented on SOLR-133:
-------------------------------
haven't reviewed any patches, but to address some of J.J.s earlier points: i
assume the goal would be to move to STaX because it is reportadly as fast as
XPP but is also the new standard for "fast" stream based processing.
As for replacing other XML parsing code in the solr code base -- XML parsing
can probably be divided into two lumps:
1) processing input streams for updates (or more generally: "requests with
ContentStreams" based on some of Ryan's recent patches)
2) config file parsing
while STaX sounds like it makes a lot of sense for #1, sticking with DOM
parsing for #2 seems like a good idea ... using XPath to access arbitrary
sections of config information is extremely handy and the performance issues
with initialization from the config DOM doens't seem like a big issue.
> change XmlUpdateRequestHandler to use StAX instead of XPP
> ---------------------------------------------------------
>
> Key: SOLR-133
> URL: https://issues.apache.org/jira/browse/SOLR-133
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Attachments: SOLR-133-XmlUpdateRequestHandler-StAX-139.patch,
> SOLR-133.diff, SOLR-133.diff
>
>
> there has been discussion of using StAX for XML parsing of updates instead of
> XPP ... opening an issue to track it as a possible improvement (orriginally
> mentioned in SOLR-61, but that task was more specificly about refactoring the
> existing code)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
