Thx Jeon. That worked. Now both the fields are returned in the response.
Its a bit inefficient but works neverthless.
Suchi
On Sat, Nov 15, 2014 at 10:44 PM, Jeon Woosung
wrote:
> I guess that I caused by shard which return renamed field.
>
> following code is source code of solr 4.6
> =
I guess that I caused by shard which return renamed field.
following code is source code of solr 4.6
===
986:if ((sreq.purpose & ShardRequest.PURPOSE_GET_FIELDS) != 0) {
987: boolean retur
https://issues.apache.org/jira/browse/SOLR-6744 created.
And hopefully correctly, since that’s my first.
On Nov 15, 2014, at 9:12 AM, Garth Grimm
mailto:garthgr...@averyranchconsulting.com>>
wrote:
I see the same issue on 4.10.1.
I’ll open a JIRA if I don’t see one.
I guess the best immediate
I see the same issue on 4.10.1.
I’ll open a JIRA if I don’t see one.
I guess the best immediate work around is to copy the unique field, and use
that field for renaming?
> On Nov 15, 2014, at 3:18 AM, Suchi Amalapurapu wrote:
>
> Solr version:4.6.1
>
> On Sat, Nov 15, 2014 at 12:24 PM, Jeon W
Solr version:4.6.1
On Sat, Nov 15, 2014 at 12:24 PM, Jeon Woosung
wrote:
> Could you let me know version of the solr?
>
> On Sat, Nov 15, 2014 at 5:05 AM, Suchi Amalapurapu
> wrote:
>
> > Hi
> > Getting the following exception when using fl renaming with unique key in
> > the schema.
> > http:/
Could you let me know version of the solr?
On Sat, Nov 15, 2014 at 5:05 AM, Suchi Amalapurapu
wrote:
> Hi
> Getting the following exception when using fl renaming with unique key in
> the schema.
> http:///solr//select?q=dress&fl=a1:p1
>
> where p1 is the unique key for
> For collections with s
Hi
Getting the following exception when using fl renaming with unique key in
the schema.
http:///solr//select?q=dress&fl=a1:p1
where p1 is the unique key for
For collections with single shard, this works flawlessly but results in the
following exception in case of multiple shards.
How do we fix
