lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Khludnev (JIRA)" <>
Subject [jira] [Commented] (SOLR-3535) Add block support for XMLLoader
Date Wed, 13 Jun 2012 09:37:42 GMT


Mikhail Khludnev commented on SOLR-3535:


do you mean XMLLoader (as well as other ones) should produce some form of hierarchical document
and some update processor will linearize such hierarchy into the sequence and pass it into

also how do you suggest to model doc hierarchy: as a SolrInputDoc subclass with explicit relations
collections or some magic collections values in the current SolrInputDocument? 

I'd like to emphasize the overall complexity - parent doc can have _several_ subdocs relations
like SKUs/UPCs and Discounts, etc   

PS pls check the parent issue SOLR-3076. there is a dilemma which feature set to provide,
your proposal is closer to "magic-knows-everything" schema approach. I don't have strong disagreement
about it, but just want to start from pretty neat ability first. Anyway, looking forward to
hear your suggestions. 

> Add block support for XMLLoader
> -------------------------------
>                 Key: SOLR-3535
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>          Components: update
>    Affects Versions: 4.1, 5.0
>            Reporter: Mikhail Khludnev
>            Priority: Minor
>         Attachments: SOLR-3535.patch
> I'd like to add the following update xml message:
> <add-block>
>     <doc>....</doc>
>     <doc>....</doc>
> </add-block>
> out of scope for now: 
> * other update formats
> * update log support (NRT), should not be a big deal
> * overwrite feature support for block updates - it's more complicated, I'll tell you
> Alt
> * wdyt about adding attribute to the current tag {pre}<add block="true">{pre} 
> * or we can establish RunBlockUpdateProcessor which treat every <add> ....</add>
as a block.
> *Test is included!!*
> How you'd suggest to improve the patch?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message