Hi !
I was previously using field(..) to escape some parameter on field name.
Like this:
fl=field(my:data)
Not good to use it on binary data as you will get "Can't initialize
DocTermsIndex to generate (function) FunctionValues for field:
my:data"
So now I use
fl=my*data
And it work's like a c
This may have been introduced by changes made to solve
https://issues.apache.org/jira/browse/SOLR-5968
I created https://issues.apache.org/jira/browse/SOLR-6501 to track the new
bug.
On Tue, Sep 9, 2014 at 4:53 PM, Mike Hugo wrote:
> Hello,
>
> With Solr 4.7 we had some queries that return dyna
Hello,
With Solr 4.7 we had some queries that return dynamic fields by passing in
a fl=*_exact parameter; this is not working for us after upgrading to Solr
4.10.0. This appears to only be a problem when requesting wildcarded
fields via SolrJ
With Solr 4.10.0 - I downloaded the binary and set up
Thanks for your answers. The problem with the use of the field function is
that it only works for non multivalued fields.
Regards.
El 28/11/2013 15:54, "Jack Krupansky" escribió:
> If you have chosen to use improper field names, then in the fl parameter
> you need to referenc
If you have chosen to use improper field names, then in the fl parameter you
need to reference them using the "field" function:
fl=id,field(01text)
The basic concept is that Solr doesn't ban improper field names, but that
they don't work in all contexts.
-- Jack Krup
On Thursday, November 28, 2013 3:59 PM, Alvaro Cabrerizo
wrote:
The question:
¿Is there a way to avoid field expansion when adding
fl<http://wiki.apache.org/solr/CommonQueryParameters#fl>parameter to
the request?
The environment:
Solr 4.4 using the next schema.xml
The test ha
The question:
¿Is there a way to avoid field expansion when adding
fl<http://wiki.apache.org/solr/CommonQueryParameters#fl>parameter to
the request?
The environment:
Solr 4.4 using the next schema.xml
The test has been done importing the next data:
{"id": "1&qu
: reference to a few "special" values, such as "id" and "score". Neither
: of them are technically "stored" fields either, but afaik you dont need
: to use "field(id), field(score)" for those. Can you honestly say that
: is consistent?
Nope.
I wasn't defending the quirks of the API, or tryi
.
Going off of the apache wiki docs (which perhaps is not the correct place to go
for documentation buts its what google gives me :-})
http://wiki.apache.org/solr/CommonQueryParameters
The fl parameter doesnt actually mention stored. It actually gives reference
to a few "special" values, s
: Yes that worked, thanks Alan. The consistency of this api is "challenging".
It's important to understand what's happening here.
fl, by default, only returns "stored" fields -- but you can also request
"psuedo-fields" such as the results of functions, or the result of a "Doc
Transformer" ...
Yes that worked, thanks Alan. The consistency of this api is "challenging".
C
On Jul 14, 2013, at 11:03 AM, Alan Woodward wrote:
> Hi Chris,
>
> Try wrapping the field name in a field() function in your fl parameter list,
> like so:
> fl=field(eff_field
Hi Chris,
Try wrapping the field name in a field() function in your fl parameter list,
like so:
fl=field(eff_field_name)
Alan Woodward
www.flax.co.uk
On 14 Jul 2013, at 18:41, Chris Collins wrote:
> Why would I be re-indexing an external file field? The whole purpose is that
> its b
dissecting.
>
> Did you reindex when you changed the schema? Sorting uses indexed
> values, not stored values. The fl parameter requires the stored values.
> These are separate within the index, and one cannot substitute for the
> other. If you didn't reindex, then you
questions I guess it should work. I will
> continue dissecting.
Did you reindex when you changed the schema? Sorting uses indexed
values, not stored values. The fl parameter requires the stored values.
These are separate within the index, and one cannot substitute for the
other. If you didn
Yep I did switch on stored=true in the field type. I was able to confirm a few
ways that there are values for the eff by two methods:
1) changing desc to asc produced drastically different results.
2) debugging FileFloatSource the following was getting triggered filling the
vals array:
Did you store the field? I.e. set stored="true"? And does the EFF contain
values for the docs you're returning?
Best
Erick
On Sun, Jul 14, 2013 at 3:32 AM, Chris Collins wrote:
> I am playing with external file field for sorting. I created a dynamic field
> using the ExternalFileField type.
>
I am playing with external file field for sorting. I created a dynamic field
using the ExternalFileField type.
I naively assumed that the "fl" argument would allow me to return the value the
external field but doesnt seem to do so.
For instance I have a defined a dynamic field:
*_efloat
th
On 24 June 2013 13:10, Upayavira wrote:
> Or use update processors, such as the script update processor. Have one
> field that is for needing purposes, and another that is for
> storage/display.
>
> If the point is to obscure the account number, shipping it in the HTML
> and having CSS do it is to
Or use update processors, such as the script update processor. Have one
field that is for needing purposes, and another that is for
storage/display.
If the point is to obscure the account number, shipping it in the HTML
and having CSS do it is too late, isn't it?
Upayavira
On Mon, Jun 24, 2013,
On 24 June 2013 10:48, sathish_ix wrote:
> Hi,
>
> Can write the query like this way ?
> I need to append *** to returned field, is this possible.
>
> account_number has last 4 character
> account_name has full name of the account
>
> I need to append *** front of account number. Instead of handli
do this ?
http://localhost:9980/solr/select?q=*:*&fl=***account_number,account_name
Thanks,
Sathish
--
View this message in context:
http://lucene.472066.n3.nabble.com/Appending-a-value-to-fl-parameter-tp4072624.html
Sent from the Solr - User mailing list archive at Nabble.com.
This appears to be the case. "*" is the only wildcard supported by "fl"
before 4.0.
-- Jack Krupansky
-Original Message-
From: Josh Harness
Sent: Wednesday, July 04, 2012 9:08 AM
To: solr-user@lucene.apache.org
Subject: fl Parameter and Wildcards for Dynamic Fi
I'm using SOLR 3.3 and would like to know how to return a list of dynamic
fields in my search results using a wildcard with the fl parameter. I found
SOLR-2444 <https://issues.apache.org/jira/browse/SOLR-2444> but this
appears to be for SOLR 4.0. Am I correct in assuming this isn&#
ossible to get a query on an "fl" value.
> For now my url query looks like that:
>
> /solr/select/?q=keyword&version=2.2&start=0&rows=10&indent=on&fl=id+name+title
>
> it works but I need request also on a "fl" parameter value.
> I'd li
n=2.2&start=0&rows=10&indent=on&fl=id+name+title
>
> it works but I need request also on a "fl" parameter value.
> I'd like to add to my initial query a kind of: WHERE the "fl" id value is
> equal to 12 OR 45 OR 32.
>
> How can I do that ?
&
Hi all,
I'd like to know if it's possible to get a query on an "fl" value.
For now my url query looks like that:
/solr/select/?q=keyword&version=2.2&start=0&rows=10&indent=on&fl=id+name+title
it works but I need request also on a "fl" parameter
Hi,
Is there any support for glob in the 'fl' param. This would be very useful
in case of retrieving dynamic fields. I have read the wiki for
FieldAliasesAndGlobsInParams. Is there any related patch?
Thanks for any pointers,
Samarth
if you wish to search on fields using wild-card you have to use a
copyField to copy all the values of "Bool_*" to another field and
search on that field.
On Tue, Dec 29, 2009 at 4:14 AM, Harsch, Timothy J. (ARC-TI)[PEROT
SYSTEMS] wrote:
> I use dynamic fields heavily in my SOLR config. I would
On Tue, Dec 29, 2009 at 4:14 AM, Harsch, Timothy J. (ARC-TI)[PEROT SYSTEMS]
wrote:
> I use dynamic fields heavily in my SOLR config. I would like to be able to
> specify which fields should be returned from a query based on a pattern for
> the field name. For instance, given:
>
>
I use dynamic fields heavily in my SOLR config. I would like to be able to
specify which fields should be returned from a query based on a pattern for the
field name. For instance, given:
I might be able to construct a query like:
http://localhost:8080/solr/select?q=Bool_*:true&r
: Anyone able to help with the question below?
dealing with "fl" is a delicate dance in Solr right now .. complicated by
both FieldSelector logic and distributed search (where both DocList and
SolrDocumentList objects need to be dealt with).
I looked at this recently and even I can't remembe
1:36 PM
To: solr-user@lucene.apache.org; yo...@lucidimagination.com
Subject: RE: fl parameter
If I were to add that capability, could I do it simply by registering my own
RequestHandler and subclassing StandarRequestHandler?
Or would I have to add an enhancement to Solr?
-Original Me
: Wednesday, April 22, 2009 11:22 AM
To: solr-user@lucene.apache.org
Subject: Re: fl parameter
On Wed, Apr 22, 2009 at 1:18 PM, Harsch, Timothy J. (ARC-SC)[PEROT
SYSTEMS] wrote:
> Since SOLR uses variable fields per record it would be useful to not only be
> able to specify which fields to retur
On Wed, Apr 22, 2009 at 1:18 PM, Harsch, Timothy J. (ARC-SC)[PEROT
SYSTEMS] wrote:
> Since SOLR uses variable fields per record it would be useful to not only be
> able to specify which fields to return in a query via the fl parameter, but
> to also specify which fields to *not* retu
Since SOLR uses variable fields per record it would be useful to not only be
able to specify which fields to return in a query via the fl parameter, but to
also specify which fields to *not* return in the query. Especially if you use
dynamic fields as there may be no way to tell ahead of time
35 matches
Mail list logo
