Re: Removing message_raw_header prefix from field names

That is probably a configuration in solrconfig.xml for the extract handler. If so, you should be able to modify it easily. Regards, Alex On Mon, Jul 15, 2019, 12:46 PM Zheng Lin Edwin Yeo, wrote: > Hi, > > When I index EML files to Solr, I realised that there are certain fields > which are

Removing message_raw_header prefix from field names

Hi, When I index EML files to Solr, I realised that there are certain fields which are prefix with message_raw_header (Eg: message_raw_header_x_receiver). There is no message_raw_header prefix in the EML files. Is there any way that we can remove the message_raw_header for all the fields directly

Re: Alias field names when searching (not for results)

: > defType=edismax q=sysadmin name:Mike qf=title text last_name : > first_name : : Aside: I'm curious about the use of "qf", here. Since I didn't want my : users to have to specify any particular field to search, I created an : "all" field and dumped everything into it. It seems like it would

Re: Alias field names when searching (not for results)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chris, On 7/24/18 1:40 PM, Chris Hostetter wrote: > > : So if I want to alias the "first_name" field to "first" and the : > "last_name" field to "last", then I would ... do what, exactly? > > se the last example here... > > https://lucene.apache.

Re: Alias field names when searching (not for results)

: So if I want to alias the "first_name" field to "first" and the : "last_name" field to "last", then I would ... do what, exactly? se the last example here... https://lucene.apache.org/solr/guide/7_4/the-extended-dismax-query-parser.html#examples-of-edismax-queries defType=edismax q=sysadmin

Re: Alias field names when searching (not for results)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Emir, On 3/6/18 2:42 AM, Emir Arnautović wrote: > I did not try it, but the first thing that came to my mind is to > use edismax’s ability to define field aliases, something like > f.f1.fq=field_1. Note that it is not recommended to have field > na

Re: Alias field names when searching (not for results)

are on an > intranet. Nope, we have a web application between the user and Solr. But I would rather not parse the user's query string and re-write it so that the search field-names are canonicalized. Thanks, - -chris > On March 6, 2018 2:42:26 AM EST, "Emir Arnautović" > wrote:

Storing documents with multiple equivalent field names

Hi all, I have a unique situation that I’m not quite sure how to approach. In my current Solr collection, I have documents that look like this: { “fieldA”: 1, “fieldB”: 2, “fieldC”: 3 } We’re adding a new “type” of document, that looks like this: { “fieldD”: 1, “fieldE”: 2, “fieldF”: 3 } Th

Re: Alias field names when searching (not for results)

Christopher The first thing that came to mind is that you are planning not to have an app in front of Solr. Without a web app, you will need to trust whoever can get access to Solr. Maybe you are on an intranet. Thanks -- Rick On March 6, 2018 2:42:26 AM EST, "Emir Arnautović" wrote: >Hi, >I d

Re: Alias field names when searching (not for results)

Hi, I did not try it, but the first thing that came to my mind is to use edismax’s ability to define field aliases, something like f.f1.fq=field_1. Note that it is not recommended to have field name starting with number so not sure if it will work with “1”. HTH, Emir -- Monitoring - Log Managem

Alias field names when searching (not for results)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I'd like for users to be able to search a field by multiple names without performing a "copy-field" when analyzing a document. Is that possible? Whenever I search for "solr alias field" I get results about how to re-name fields in the results.

Re: Multiple mapping types sharing some field names with different datatypes

Thank you Shawn for the detailed explanation. I've posted this also in SO (with examples): https://stackoverflow.com/questions/44181274/solr-mapping-types-sharing-field-name-but-different-datatype this will shed some light on your mystery :) On Thu, May 25, 2017 at 4:01 PM, Shawn Heisey wrote:

Re: Multiple mapping types sharing some field names with different datatypes

On 5/25/2017 1:49 AM, Yarden Bar wrote: > A question about collection (or mapping, I'm an ES user). > > I have a use-case where I index AWS CloudTrail logs. currently, in ES, I > use the CT eventName as document type for dynamic mapping. > There are several event types which use the same field name

Multiple mapping types sharing some field names with different datatypes

Hi all, A question about collection (or mapping, I'm an ES user). I have a use-case where I index AWS CloudTrail logs. currently, in ES, I use the CT eventName as document type for dynamic mapping. There are several event types which use the same field name but with different datatype. Example: ev

Re: How to get field names of dynamic field

Ugh. Ok, so if the list is different per-request, you should probably look at writing a custom search component if you want to keep it all in Solr layer. But really, you have middle-ware, right? Why don't you formulate your query with all the business requirement specifics in there. Regards,

Re: How to get field names of dynamic field

Here if i am saying dynamic say *by_* *is the field then by_color, by_size .. etc . would be the dynamic fields . Regards, Abhishek Tiwari On Mon, Apr 17, 2017 at 1:47 PM, Midas A wrote: > Thanks alex, > > I want all dynamic fields related to a query( i.e. category_id : 199 > where 199 catego

Re: How to get field names of dynamic field

Thanks alex, I want all dynamic fields related to a query( i.e. category_id : 199 where 199 category has around 1 docs) . How we can get this with help of luke Request handler. On Mon, Apr 17, 2017 at 1:39 PM, Alexandre Rafalovitch wrote: > You could externalize that by periodically: > 1)

Re: How to get field names of dynamic field

You could externalize that by periodically: 1) Running a luke query or Schema API to get the list of fields 2) Running Request Parameter API to update the list of field to return (this does not cause core reload) 3) If you have permanent field list on top of dynamic ones, you could use parameter su

Re: How to get field names of dynamic field

Can we do faceting for all fields created by dynamically created fields rather sending explicitly sending it by query will facet.fields=*by_* * work or any other alternate ?? I was thinking that i will get all dynamic fields with help of Luke handler . But probably it is not possible through luke

Re: How to get field names of dynamic field

Hi Midas, LukeRequestHandler shows that information. Ahmet On Friday, April 14, 2017, 1:16:09 PM GMT+3, Midas A wrote: Actually , i am looking for APi On Fri, Apr 14, 2017 at 3:36 PM, Andrea Gazzarini wrote: > I can see those names in the "Schema  browser" of the admin UI, so I guess > usin

Re: How to get field names of dynamic field

Actually , i am looking for APi On Fri, Apr 14, 2017 at 3:36 PM, Andrea Gazzarini wrote: > I can see those names in the "Schema browser" of the admin UI, so I guess > using the (lucene?) API it shouldn't be hard to get this info. > > I don' know if the schema api (or some other service) offer t

Re: How to get field names of dynamic field

I can see those names in the "Schema browser" of the admin UI, so I guess using the (lucene?) API it shouldn't be hard to get this info. I don' know if the schema api (or some other service) offer this service Andrea On 14 Apr 2017 10:03, "Midas A" wrote: > Hi, > > > Can i get all the field c

How to get field names of dynamic field

Hi, Can i get all the field created for dynamic field in solr . Like my dynamic field is by_* and i have index by_color by_size .. etc I want to retrieve all these field name . Is there any way to do this based on some query

Re: Solr: Return field names that contain search term

Hi rahul, I am working on a similar scenario, was wondering if you find a way to resolve this. Thanks in advance! -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Return-field-names-that-contain-search-term-tp3329993p4321399.html Sent from the Solr - User mailing list

Re: Solr Schema for same field names within different input entities

Thanks a lot Eric. Thanks and Regards Aniruddh On Fri, Jun 10, 2016 at 12:25 PM, Erick Erickson wrote: > Usually people put an application layer between the Business User and > the actual query to form complex Solr queries that "do the right > thing". Unfortunately there's no good automated way

Re: Solr Schema for same field names within different input entities

Usually people put an application layer between the Business User and the actual query to form complex Solr queries that "do the right thing". Unfortunately there's no good automated ways to do this that I know of as each app has its own set of peculiarities. Best, Erick On Wed, Jun 8, 2016 at 2:

Re: Solr Schema for same field names within different input entities

Hi Eric Thanks for prompt response. The reason for not flattening in given format was (this I used as example for a very simple data structure). But in actual my record has 100 of fields like this with different nesting inside. and once I ingest data in Solr , then Business User will make a searc

Re: Solr Schema for same field names within different input entities

Why not just flatten this? I.e. have fields prev_temp day_temp next_temp prev_humidity day_humitidy next_humidity ? If you use multiValued fields, there's no good way to express prev_temp=X AND prev_humidity=Y because they'd both be in a single MV field called "temp" and "humidity" so querying tem

Re: Solr Schema for same field names within different input entities

Hi Susheel Thanks for prompt response. I have a further query on it. Wouldn't above mentioned approach be appropriate if I am either getting PreviousDay or CurrentDay. In my case I will sometimes be getting both PreviousDay and CurrentDay in same record. so when I store temp/humidity as multi-v

Re: Solr Schema for same field names within different input entities

How about creating schema with temperature, humidity & a day field (and other fields you may have like zipcode/city/country etc). Put day="next" or day="previous" and during query use fq (filter query) to have fq=day:previous or fq=day:next. Thanks, Susheel On Wed, Jun 8, 2016 at 2:46 PM, Anirudd

Solr Schema for same field names within different input entities

Hi Request help I have following XML data to start with 13 50 15 60 Please notice it has "previousDay" and "nextDay" and both of them contains details of same field "temperature" and "humidity" What is best way to create schema for it , where I coul

Re: Specifying dynamic field type without polluting actual field names with type indicators

> > > > 2016-05-19 15:30 GMT+02:00 Steve Rowe : > > > Peter, > > > > It’s an interesting idea. Could you make a Solr JIRA? > > > > I don’t know where the field type specification would go, but providing a > > mechanism to specify field type for previou

Re: Specifying dynamic field type without polluting actual field names with type indicators

: > Peter, > > It’s an interesting idea. Could you make a Solr JIRA? > > I don’t know where the field type specification would go, but providing a > mechanism to specify field type for previously non-existent fields, outside > of the field names themselves, seems useful. &

Re: Specifying dynamic field type without polluting actual field names with type indicators

Peter, It’s an interesting idea. Could you make a Solr JIRA? I don’t know where the field type specification would go, but providing a mechanism to specify field type for previously non-existent fields, outside of the field names themselves, seems useful. In the meantime, do you know about

Re: Specifying dynamic field type without polluting actual field names with type indicators

Hi Steve, Yes, I know the schema API, however I do not want to specify the field type problematically for every single field. I would like to be able to specify the field type when it is being added (similar to the name postfixes, but without affecting the field names). Thanks, Peter 2016-05

Re: Specifying dynamic field type without polluting actual field names with type indicators

ot want to keep using > post-fixes while running queries... Dynamic fields are just a different way to specify field names. Instead of explictly naming the field, you can put a * at the beginning or end of the name and define an entire series of potential field names with one declaration, and tie thos

Re: Specifying dynamic field type without polluting actual field names with type indicators

Hi Peter, Are you familiar with the Schema API?: You can use it to create fields, field types, etc. prior to ingesting your data. -- Steve www.lucidworks.com > On May 17, 2016, at 11:05 AM, Horváth Péter Gergely > wrote: > > Hi A

Specifying dynamic field type without polluting actual field names with type indicators

Hi All, By default Solr allows you to define the type of a dynamic field by appending a post-fix to the name itself. E.g. creating a color_s field instructs Solr to create a string field. My understanding is that if we do this, all queries must refer the post-fixed field name as well. So instead o

Specifying dynamic field type without polluting actual field names with type indicators

Hi All, By default Solr allows you to define the type of a dynamic field by appending a post-fix to the name itself. E.g. creating a color_s field instructs Solr to create a string field. My understanding is that if we do this, all queries must refer the post-fixed field name as well. So instead o

Re: Dollar signs in field names

n use dollar signs, but there won't be any attempts > > to support it if some component somewhere doesn't "do the > > right thing" with it. And no guarantee that there aren't current > > corner cases where that causes problems. And if it does cause > &

Re: Dollar signs in field names

to support it if some component somewhere doesn't "do the > right thing" with it. And no guarantee that there aren't current > corner cases where that causes problems. And if it does cause > problems, support won't be added. > > Best, > Erick > &

Re: Dollar signs in field names

s cause problems, support won't be added. Best, Erick On Mon, Jul 27, 2015 at 10:42 AM, Thomas Seidl wrote: > Hi all, > > I've used dollar signs in field names for several years now, as an easy > way to escape "bad" characters (like colons) coming in from the or

Dollar signs in field names

Hi all, I've used dollar signs in field names for several years now, as an easy way to escape "bad" characters (like colons) coming in from the original source of the data, and I've never had any problems. Since I don't know of any Solr request parameters that use a

Re: How to identify field names from the suggested values in multiple fields

There shouldn't be any limitation. You haven't provided the full stack trace, so there's not a lot to say. Do be a little careful, though, since the parameters are slightly different for analyzingInfix, i.e. indexPath rather than sotreDir. Best, Erick On Thu, Jun 4, 2015 at 4:55 AM, Dhanesh Radh

Re: How to identify field names from the suggested values in multiple fields

Dear Erick, That document help me to build multiple suggesters But still there is one problem that I faced. When I used both suggesters with same lookupImpl as AnalyzingInfixLookupFactory AnalyzingInfixLookupFactory solr throws an error Caused by: java.lang.RuntimeException at org.apache.

Re: How to identify field names from the suggested values in multiple fields

Yes, this might help: http://lucidworks.com/blog/solr-suggester/ Best, Erick On Wed, Jun 3, 2015 at 10:32 PM, Dhanesh Radhakrishnan wrote: > Thank you for the quick response. > If I use 2 suggesters, can I get the result in a single request? > http://192.17.80.99:8983/solr/core1/suggest?suggest=

Re: How to identify field names from the suggested values in multiple fields

Thank you for the quick response. If I use 2 suggesters, can I get the result in a single request? http://192.17.80.99:8983/solr/core1/suggest?suggest=true&suggest.dictionary=mySuggester&wt=xml&suggest.q=school Is there any helping document to build multiple suggesters?? On Thu, Jun 4, 2015 at 10

Re: How to identify field names from the suggested values in multiple fields

Configure two suggesters, one based on each field. Use both of them and you’ll get separate suggestions from each. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) On Jun 3, 2015, at 10:03 PM, Dhanesh Radhakrishnan wrote: > Hi > Anyone help me to build

How to identify field names from the suggested values in multiple fields

Hi Anyone help me to build a suggester auto complete based on multiple fields? There are two fields in my schema. Category and Subcategory and I'm trying to build suggester based on these 2 fields. When the suggestions result, how can I distinguish from which filed it come from? I used a copyfie

Re: Solr: Elevate with complex query specifying field names

ck.collate=true&hl=true&rows=1000 > > Now, I want to add query elevation to my mix. I got it to work pretty > flawlessly, however, I'm not sure how to get it to work with my queries > as they specifically state field names and especially boosts on a > regular basis. > >

Solr: Elevate with complex query specifying field names

&wt=json&spellcheck.collate=true&hl=true&rows=1000 Now, I want to add query elevation to my mix. I got it to work pretty flawlessly, however, I'm not sure how to get it to work with my queries as they specifically state field names and especially boosts on a regular

Re: Field Names

On 11 June 2013 16:48, PeriS wrote: > > Nothing wrong and would work too, but I wanted to see if I could restrict > it more as per the schema at http://www.loc.gov/marc/bibliographic/. [...] As per your other messages, constructing the query is under your control. So, why do you care about such r

Re: Field Names

And besides, the user is not going to be aware of the actual field names to query on - its abstracted to some simple names like author which could be a combination of 100a,b which the application would know how to construct based on an external configuration etc… You see what i mean. On Jun 11

Re: Field Names

Nothing wrong and would work too, but I wanted to see if I could restrict it more as per the schema at http://www.loc.gov/marc/bibliographic/. On Jun 10, 2013, at 10:09 PM, Gora Mohanty wrote: > What is wrong with, e.g., > stored="true"/> > > Regards, > Gora

Re: Field Names

on is aware of the schema, they know how to query the fields or what to query for. Does that make sense? On Jun 10, 2013, at 10:48 PM, Jack Krupansky wrote: > One idea: DON'T DO IT! > > Seriously, if you find yourself trying to "play games" with field names, it > sa

Re: Field Names

One idea: DON'T DO IT! Seriously, if you find yourself trying to "play games" with field names, it says that you probably have a data model that is grossly out of line with the strengths (and weaknesses) of Solr. Dynamic fields are fine - when used in moderation, but not

Re: Field Names

On 11 June 2013 07:24, PeriS wrote: > > I was wondering if there was a way to define field names that are more less > dynamic in nature but follow a regular expression pattern. I know you can > have asterisk either as a prefix or a suffix but not both or somewhere int he > m

Field Names

I was wondering if there was a way to define field names that are more less dynamic in nature but follow a regular expression pattern. I know you can have asterisk either as a prefix or a suffix but not both or somewhere int he middle of a name. Goal: to define a field that takes up the form

Re: Solr 4.2.1 behavior with field names that use "|" character

is NOT guaranteed to work in all contexts, nor guaranteed to work in the future. Function queries and the "fl" parameter are two great examples - both now support a complex syntax, and only recognize Java names. It has always been a really bad idea to use non-indentifiers for S

Re: Solr 4.2.1 behavior with field names that use "|" character

t as an ignored field (since we can just do a > q=state|city:ca|* to find all entries in California). > > Is this a known issue? Is there any way to disable the parsing of field names > in a field list? > > Thanks, > > -- Ken > > -- > Ken Krugler > +1 530-210-6378 > http://www.scaleunlimited.com > custom big data solutions & training > Hadoop, Cascading, Cassandra & Solr > > > > >

Solr 4.2.1 behavior with field names that use "|" character

s this a known issue? Is there any way to disable the parsing of field names in a field list? Thanks, -- Ken -- Ken Krugler +1 530-210-6378 http://www.scaleunlimited.com custom big data solutions & training Hadoop, Cascading, Cassandra & Solr

Re: Schema Field Names i18n

Will a field have different names in different languages? There is no facility for 'aliases' for field name. Erick is right, this sounds like you need query and update components to implement this. Also, you might try using URL-encoding for the field names. This would save my sanity.

Re: Schema Field Names i18n

There's no really easy way that I know of. I've seen several approaches used though 1> do it in the UI. This assumes that your users aren't typing in raw queries, they're picking field names from a drop-down or similar. Then the UI maps the chosen fields into what the schem

Schema Field Names i18n

Anyone have experience with internationalizing the field names in the SOLR schema, so users in different languages can specify fields in their own language? My first thoughts would be to create a custom search component or query parser than would convert localized field names back to the

Re: Apply clustering to field names?

Per: 1> relevancy sorting on field names: First, you have to define what that means ... Relavant to your query terms? Relevant by the count of field names in a particular document? Under any circumstances, this seems like it's heading towards some kind of analytics. Take a look at Functio

Re: Apply clustering to field names?

> I want the user to be able to select from relevant properties >> and property values, adding them iteratively/interactively to the query to >> refine the result set. >> >> *How I do this at the moment:* >> I scrape field names from the result set and display them

Re: Apply clustering to field names?

g to accomplish:* > I want the user to be able to select from relevant properties > and property values, adding them iteratively/interactively to the query to > refine the result set. > > *How I do this at the moment:* > I scrape field names from the result set and display them in a si

Re: Designing an index with multiple entity types, sharing field names across entity-types.

2012 at 2:04 AM, santamaria2 wrote: > *civilized bump* > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Designing-an-index-with-multiple-entity-types-sharing-field-names-across-entity-types-tp3999727p451.html > Sent from the Solr - User mailing list archive at Nabble.com.

Re: Designing an index with multiple entity types, sharing field names across entity-types.

*civilized bump* -- View this message in context: http://lucene.472066.n3.nabble.com/Designing-an-index-with-multiple-entity-types-sharing-field-names-across-entity-types-tp3999727p451.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Designing an index with multiple entity types, sharing field names across entity-types.

To clarify a wee bit more. I'm wondering the performance impact on single-entity queries if I use common field names. eg. 'name' field for all entity types. 'Author' & 'Book' together make up for 200,000+ 'name' values. Will this affect an

Designing an index with multiple entity types, sharing field names across entity-types.

which I haven't decided on how I'd go about designing a query, yet. What say thee? -- View this message in context: http://lucene.472066.n3.nabble.com/Designing-an-index-with-multiple-entity-types-sharing-field-names-across-entity-types-tp3999727.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Problems with field names in solr functions

In trunk, see: * SOLR-2335: New 'field("...")' function syntax for refering to complex field names (containing whitespace or special characters) in functions. The schema in trunk also specifies: -Yonik http://lucidimagination.com On Thu, May 10, 2012 at 11:28 AM, Iker

Re: Problems with field names in solr functions

I know there are edge cases where "odd" field naming causes problems, field names not well-defined/enforced with Solr. Rather than banging my head against the wall and finding these cases at inopportune moments, I'd confine myself to lower-case and underscores. Other stuff _

Re: Field names w/ leading digits cause strange behavior

Thank you for verifying the issue. I've created a ticket at https://issues.apache.org/jira/browse/SOLR-3407 -- View this message in context: http://lucene.472066.n3.nabble.com/Field-names-w-leading-digits-cause-strange-behavior-tp3936354p3936599.html Sent from the Solr - User mailing

Re: Field names w/ leading digits cause strange behavior

get back that value as well as the behavior above. > ... > > true > 24 > > ... > > Is it ok the have fields that start with digits? If so, is there a different > way to specify them using the "fl" parameter? Thanks! > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Field-names-w-leading-digits-cause-strange-behavior-tp3936354p3936354.html > Sent from the Solr - User mailing list archive at Nabble.com.

Field names w/ leading digits cause strange behavior

erent way to specify them using the "fl" parameter? Thanks! -- View this message in context: http://lucene.472066.n3.nabble.com/Field-names-w-leading-digits-cause-strange-behavior-tp3936354p3936354.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Document with longer field names and many fields

; fields. Depending upon the number of *unique* values in these fields, you may bet some extra memory consumption, but whether that matters depends a lot on the particulars. By a huge margin, most of the time is spent in searching itself, not parsing the field names so long ones really don'

Document with longer field names and many fields

this message in context: http://lucene.472066.n3.nabble.com/Document-with-longer-field-names-and-many-fields-tp3703077p3703077.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Distributed search has problems with some field names

Hi, On 09/29/2011 03:10 PM, Erick Erickson wrote: I know I've seen other anomalies with odd characters in field names. In general, it's much safer to use only letters, numbers, and underscores. In fact, I even prefer lowercase letters. Since you're pretty sure those work, why no

Re: Distributed search has problems with some field names

I know I've seen other anomalies with odd characters in field names. In general, it's much safer to use only letters, numbers, and underscores. In fact, I even prefer lowercase letters. Since you're pretty sure those work, why not just use them? Best Erick On Wed, Sep 28, 2011 a

Distributed search has problems with some field names

Hello all, I'm experimenting with the "Distributed Search" bits in the nightly builds and I'm facing a problem. I have on my schema.xml some dynamic fields defined like this: multiValued="true" /> When hitting a single shard the following query works fine: http:///select?q=*:*&fl=ts,$

Re: Solr: Return field names that contain search term

Thanks Chris ! Will try out the second approach you suggested and share my findings. On Mon, Sep 12, 2011 at 5:03 PM, Chris Hostetter wrote: > > : > Would highly appreciate if someone can suggest other efficient ways to > : > address this kind of a requirement. > > one approach would be to index

Re: Solr: Return field names that contain search term

: > Would highly appreciate if someone can suggest other efficient ways to : > address this kind of a requirement. one approach would be to index each attachment as it's own document and search those. you could then use things like the group collapsing features to return onlly the "main" type

Re: Solr: Return field names that contain search term

I also would like to know the answer to this. But my feeling is that you can't do what you want. I also had to use the highlighting workaround and aggregate dynamic field to accomplish the inability of multivalued fields to accommodate it. On Mon, 12 Sep 2011 11:44:01 -0400, Rahul Warawdekar wro

Solr: Return field names that contain search term

Hi, I have a a query on Solr search as follows. I am indexing an entity which includes a multivalued field using DIH. This multivalued field contains content from multiple attachments for a single entity. Now, for eg. if i search for the term "solr", will I be able to know which field contains t

Re: Getting all field names in a Solr index via SolrJ

Sure, I just attempted to use the term as a shorthand. :-) The schema browser that the web admin interface uses, however, makes Ajax calls to the LukeRequestHandler. Has anyone implemented this in pure Java? On Sat, Jun 11, 2011 at 4:43 AM, Chris Hostetter wrote: > > : Yes. So the consensus is

Re: Getting all field names in a Solr index via SolrJ

: Yes. So the consensus is that it can only be done via Luke. I would expect : it to be easier than that. Luke != LukeRequestHandler LukeRequestHandler is built into solr, and is *exactly* how the web ui of Solr lists all the fields. http://wiki.apache.org/solr/LukeRequestHandler -Hoss

Re: Getting all field names in a Solr index via SolrJ

you use &numTerms=0 things will be fast. > By the way if you dont care about dynamic fields, you can extract field > names from schema.xml too (via ShowFileRequestHandler) >

Re: Getting all field names in a Solr index via SolrJ

> Yes. So the consensus is that it can > only be done via Luke. I would expect > it to be easier than that. If you use &numTerms=0 things will be fast. By the way if you dont care about dynamic fields, you can extract field names from schema.xml too (via ShowFileRequestHandler)

Re: Getting all field names in a Solr index via SolrJ

Yes. So the consensus is that it can only be done via Luke. I would expect it to be easier than that. Thanks! On Fri, Jun 10, 2011 at 9:05 PM, Ahmet Arslan wrote: > > > Sure, but how does the web admin do > > > it without Luke? > > > > admin/analysis.jsp uses luke too. > > > > Sorry I wrote it

Re: Getting all field names in a Solr index via SolrJ

> > Sure, but how does the web admin do > > it without Luke? > > admin/analysis.jsp uses luke too. > Sorry I wrote it wrong. I was referring /admin/schema.jsp

Re: Getting all field names in a Solr index via SolrJ

t; >> If you really want to have _all_ defined (and therefore possible >> fields) you should have a look to >> http://wiki.apache.org/solr/LukeRequestHandler >> >> Regards >> Stefan >> >> On Fri, Jun 10, 2011 at 5:48 PM, Public Network Services >&

Re: Getting all field names in a Solr index via SolrJ

> Sure, but how does the web admin do > it without Luke? admin/analysis.jsp uses luke too.

Re: Getting all field names in a Solr index via SolrJ

eRequestHandler > > Regards > Stefan > > On Fri, Jun 10, 2011 at 5:48 PM, Public Network Services > wrote: > > Hi... > > > > I would like to get a list of all field names in a Solr index, much like > the > > web admin can list all these fields in Schema Br

Re: Getting all field names in a Solr index via SolrJ

If you really want to have _all_ defined (and therefore possible fields) you should have a look to http://wiki.apache.org/solr/LukeRequestHandler Regards Stefan On Fri, Jun 10, 2011 at 5:48 PM, Public Network Services wrote: > Hi... > > I would like to get a list of all field names

Getting all field names in a Solr index via SolrJ

Hi... I would like to get a list of all field names in a Solr index, much like the web admin can list all these fields in Schema Browser. It sounds trivial, but still looking around as to how it would best be implemented. If I run a query with the wildcard string ("*:*"), not all field

Re: Field names with a period (.)

On Sat, May 7, 2011 at 1:29 AM, Chris Hostetter wrote: > > : I remember the same, except I think I've seen the recommendation that you > : make all the letters lower-case. As I remember, there are some interesting > : edge cases that you might run into later with upper case. > > i can't think of *

Re: Field names with a period (.)

t param expects whitespace seperated lists of " " pairs -- if your field name contains whitespace, that can screw you up. the lucene QueryParser is another situation where punctuation and whitespace are significant, so having those characters in your field names may cause your problems (i thi

Re: Field names with a period (.)

rdo Souza >> wrote: >> > Hi guys, >> > >> > Can i have a field name with a period(.) ? >> > Like in *file.size* >> >> Cannot find now where this is documented, but from what I remember it is >> recommended to use only characters A-Z, a

Re: Field names with a period (.)

ith a period(.) ? > > Like in *file.size* > > Cannot find now where this is documented, but from what I remember it is > recommended to use only characters A-Z, a-z, 0-9, and underscore (_) in > field names, and some special characters are known to cause problems. > > Regards, > Gora >

  1   2   >