You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2009/05/02 21:00:30 UTC
[jira] Commented: (SOLR-994) EnumeratedEntityTransformer
[ https://issues.apache.org/jira/browse/SOLR-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705318#action_12705318 ]
Shalin Shekhar Mangar commented on SOLR-994:
--------------------------------------------
bq. one extra addition which I can think of is put an implicit variable 'rowsFetchedCount ' into the variableresolver so that it can be directly used .
With SOLR-989 Context exposes the statistics map so rowCount is already available. Should we close this issue?
> 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.4
>
> 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.
Re: [jira] Commented: (SOLR-994) EnumeratedEntityTransformer
Posted by Noble Paul നോബിള് नोब्ळ् <no...@gmail.com>.
But it is not yet acessible though VariableResolver
On Sun, May 3, 2009 at 12:30 AM, Shalin Shekhar Mangar (JIRA)
<ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/SOLR-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705318#action_12705318 ]
>
> Shalin Shekhar Mangar commented on SOLR-994:
> --------------------------------------------
>
> bq. one extra addition which I can think of is put an implicit variable 'rowsFetchedCount ' into the variableresolver so that it can be directly used .
>
> With SOLR-989 Context exposes the statistics map so rowCount is already available. Should we close this issue?
>
>> 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.4
>>
>> 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.
>
>
--
--Noble Paul