Re: Parsing and indexing parts of the input file paths

2015-07-22 Thread Andrew Musselman
uestion. If you're talking two different > >> fields, use copyField. > >> > >> On Wed, Jul 22, 2015 at 8:55 AM, Andrew Musselman > >> wrote: > >> > Fwding to user.. > >> > > >> > -- Forwarded message -- > >> > F

Re: Parsing and indexing parts of the input file paths

2015-07-22 Thread Erick Erickson
ur question. If you're talking two different >> fields, use copyField. >> >> On Wed, Jul 22, 2015 at 8:55 AM, Andrew Musselman >> wrote: >> > Fwding to user.. >> > >> > -- Forwarded message ------ >> > From: Andrew Mus

Re: Parsing and indexing parts of the input file paths

2015-07-22 Thread Andrew Musselman
Forwarded message -- > > From: Andrew Musselman > > Date: Wed, Jul 22, 2015 at 8:54 AM > > Subject: Re: Parsing and indexing parts of the input file paths > > To: d...@lucene.apache.org > > > > > > Thanks, and tell it to index the &q

Re: Parsing and indexing parts of the input file paths

2015-07-22 Thread Erick Erickson
gt; Subject: Re: Parsing and indexing parts of the input file paths > To: d...@lucene.apache.org > > > Thanks, and tell it to index the "id" field, which eventually contains the > file path? > > On Wed, Jul 22, 2015 at 8:48 AM, Erick Erickson > wrote: > >&

Re: Parsing and indexing parts of the input file paths

2015-07-21 Thread Andrew Musselman
Which can only happen if I post it to a web service, and won't happen if I do it through config? On Tue, Jul 21, 2015 at 2:19 PM, Upayavira wrote: > yes, unless it has been added consciously as a separate field. > > On Tue, Jul 21, 2015, at 09:40 PM, Andrew Musselman wrote: > > Thanks, so by the

Re: Parsing and indexing parts of the input file paths

2015-07-21 Thread Upayavira
yes, unless it has been added consciously as a separate field. On Tue, Jul 21, 2015, at 09:40 PM, Andrew Musselman wrote: > Thanks, so by the time we would get to an Analyzer the file path is > forgotten? > > https://cwiki.apache.org/confluence/display/solr/Analyzers > > On Tue, Jul 21, 2015 at

Re: Parsing and indexing parts of the input file paths

2015-07-21 Thread Andrew Musselman
Thanks, so by the time we would get to an Analyzer the file path is forgotten? https://cwiki.apache.org/confluence/display/solr/Analyzers On Tue, Jul 21, 2015 at 1:27 PM, Upayavira wrote: > Solr generally does not interact with the file system in that way (with > the exception of the DIH). > >

Re: Parsing and indexing parts of the input file paths

2015-07-21 Thread Upayavira
Solr generally does not interact with the file system in that way (with the exception of the DIH). It is the job of the code that pushes a file to Solr to process the filename and send that along with the request. See here for more info: https://cwiki.apache.org/confluence/display/solr/Uploading+

Re: Parsing and indexing parts of the input file paths

2015-07-21 Thread Andrew Musselman
I'm not sure, it's a remote team but will get more info. For now, assuming that a certain directory is specified, like "/user/andrew/", and a regex is applied to capture anything two directories below matching "*/*/*.pdf". Would there be a way to capture the wild-carded values and index them as f

Re: Parsing and indexing parts of the input file paths

2015-07-21 Thread Upayavira
Keeping to the user list (the right place for this question). More information is needed here - how are you getting these documents into Solr? Are you posting them to /update/extract? Or using DIH, or? Upayavira On Tue, Jul 21, 2015, at 06:31 PM, Andrew Musselman wrote: > Dear user and dev lists