[
https://issues.apache.org/jira/browse/SOLR-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-994:
----------------------------
Fix Version/s: (was: 1.4)
1.5
it is currently possible to add this Transformer explicitly. A more elegant
solution would be to make it happen automatically w/o a Transformer. It can be
a bigger initiative and i am pushing this to 1.5
> EnumeratedEntityTransformer
> ---------------------------
>
> Key: SOLR-994
> URL: https://issues.apache.org/jira/browse/SOLR-994
> Project: Solr
> Issue Type: New Feature
> Components: contrib - DataImportHandler
> Affects Versions: 1.4
> Reporter: Jared Flatow
> Assignee: Shalin Shekhar Mangar
> Priority: Minor
> Fix For: 1.5
>
> Attachments: SOLR-994.patch
>
>
> An EnumeratedEntityTransformer gives the Nth entity an accessible
> ${<entity>.n} == N. In addition, the entity may specify a chunkSize
> attribute, which will cause the chunkSize'th entity to gain the attribute
> $hasMore=true. A template for a nextUrl may also be specified on the entity,
> that is different from the url template.
> Consider an API:
> http://host:port/path/to/resource?maximum_number_returned=50&return_start_index=0
> an entity could specify:
> <entity name="myEntity" processor="XPathEntityProcessor"
> transformer="EnumeratedEntityTransformer"
> url="http://host:port/path/to/resource?maximum_number_returned=50&return_start_index=${myEntity.n}";
> chunkSize=50>...</entity>
> This allows for fetching entities in chunks until there are < chunkSize
> returned.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
