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 "Ryan McKinley (JIRA)" <ji...@apache.org> on 2007/05/10 03:33:15 UTC
[jira] Assigned: (SOLR-226) support dynamic fields as copyField
destination
[ https://issues.apache.org/jira/browse/SOLR-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McKinley reassigned SOLR-226:
----------------------------------
Assignee: Ryan McKinley
> support dynamic fields as copyField destination
> -----------------------------------------------
>
> Key: SOLR-226
> URL: https://issues.apache.org/jira/browse/SOLR-226
> Project: Solr
> Issue Type: Improvement
> Reporter: Ryan McKinley
> Assigned To: Ryan McKinley
> Priority: Minor
> Fix For: 1.3
>
> Attachments: SOLR-226-DynamicCopyField.patch, SOLR-226-DynamicCopyField.patch
>
>
> I'd like to use a dynamic field as the destination of a copyField:
> Given:
> <field name="tag_*" type="string" ... />
> <field name="text_*" type="text" ... />
> I want:
> <copyField source="tag_*" dest="text_*" />
> For background see:
> http://www.nabble.com/copyField-to-a-dynamic-field-tf2300115.html#a6419101
> http://www.nabble.com/dynamic-copyFields-tf3683816.html#a10296520
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: bug in JSON Response
Posted by Chris Hostetter <ho...@fucit.org>.
: Thanks, I should have checked the wiki.
it's also called out in the "Upgrading from Solr 1.1" section of the
CHANGES.txt file...
http://svn.apache.org/repos/asf/lucene/solr/trunk/CHANGES.txt
...
The JSON response format for facets has changed to make it easier for
clients to retain sorted order. Use json.nl=map explicitly in clients
to get the old behavior, or add it as a default to the request handler
in solrconfig.xml
-Hoss
RE: bug in JSON Response
Posted by "Gunther, Andrew" <Gu...@si.edu>.
Thanks, I should have checked the wiki.
Cheers,
Andrew
-----Original Message-----
From: yseeley@gmail.com [mailto:yseeley@gmail.com] On Behalf Of Yonik
Seeley
Sent: Thursday, May 10, 2007 9:32 AM
To: solr-dev@lucene.apache.org
Subject: Re: bug in JSON Response
On 5/10/07, Gunther, Andrew <Gu...@si.edu> wrote:
> Anyone notice an error in the JSON response when requesting facets.
>
> The response I get is:
>
{"facet_queries":{},"facet_fields":{"subject":["Landscape",10335,"River"
> ,1767,"Mountain",1278,"Architecture",1184] }}
>
> It seems like the JSONArray subject should yield a JSONObject with
> name,value pairs like:
>
>
{"subject":[{"Landscape":10335,"River":1767,"Mountain":1278,"Architectur
> e":1184}] }
>
> I've checked the bug list but nothing is showing up.
> Anyone using JSON?
The default was changed because many JSON clients don't maintain order
of key/value pairs in a JSONObject.
See http://wiki.apache.org/solr/SolJSON
If you wish to get a JSON object for "ordered" key/value pairs like
facet counts,
pass in json.nl=map
-Yonik
Re: bug in JSON Response
Posted by Yonik Seeley <yo...@apache.org>.
On 5/10/07, Gunther, Andrew <Gu...@si.edu> wrote:
> Anyone notice an error in the JSON response when requesting facets.
>
> The response I get is:
> {"facet_queries":{},"facet_fields":{"subject":["Landscape",10335,"River"
> ,1767,"Mountain",1278,"Architecture",1184] }}
>
> It seems like the JSONArray subject should yield a JSONObject with
> name,value pairs like:
>
> {"subject":[{"Landscape":10335,"River":1767,"Mountain":1278,"Architectur
> e":1184}] }
>
> I've checked the bug list but nothing is showing up.
> Anyone using JSON?
The default was changed because many JSON clients don't maintain order
of key/value pairs in a JSONObject.
See http://wiki.apache.org/solr/SolJSON
If you wish to get a JSON object for "ordered" key/value pairs like
facet counts,
pass in json.nl=map
-Yonik
bug in JSON Response
Posted by "Gunther, Andrew" <Gu...@si.edu>.
Anyone notice an error in the JSON response when requesting facets.
The response I get is:
{"facet_queries":{},"facet_fields":{"subject":["Landscape",10335,"River"
,1767,"Mountain",1278,"Architecture",1184] }}
It seems like the JSONArray subject should yield a JSONObject with
name,value pairs like:
{"subject":[{"Landscape":10335,"River":1767,"Mountain":1278,"Architectur
e":1184}] }
I've checked the bug list but nothing is showing up.
Anyone using JSON?
Cheers,
Andrew