AW: AW: AW: (auto)suggestions, but ony from a "filtered" set of documents

[Clemens Wyss DEV]

Thx Mike,
at the moment I do not see/understand what the advantage of " feed a single 
suggester from multiple fields" compared to "using copyfields to feed the 
suggester field" is? 
Also, coming back to my main issue, how does your approach allow me to "filter 
the documents to be taken into consideration for suggestions per suggestion 
request"?

-Clemens

-Ursprüngliche Nachricht-
Von: Michael Sokolov [mailto:msoko...@safaribooksonline.com] 
Gesendet: Sonntag, 26. Oktober 2014 23:07
An: solr-user@lucene.apache.org
Betreff: Re: AW: AW: (auto)suggestions, but ony from a "filtered" set of 
documents

This project (https://github.com/safarijv/ifpress-solr-plugin/) has some 
examples of custom Solr UpdateRequestProcessors that feed a single suggester 
from multiple fields, applying different weights to them, using complete values 
from some and analyzing others into tokens.

The first thing I did was FieldMergingProcessor, which creates a new field, 
kind of like copyfield, but allowing for some analysis/transformation to be 
done just prior to copying the field values.

I think a better solution is MultiSuggesterProcessor and friends, which 
multiplexes different input fields to a single suggester. It also manages NRT 
updates to AnalyzingInfixSuggester

I haven't had a chance to up good docs or generalize very much, but if you have 
questions feel free to get in touch.

-Mike

On 10/26/14 3:52 AM, Clemens Wyss DEV wrote:
>> Maybe you could use copyField to populate one field with the values
>> (fields) that you like to use for suggestions
> We intended to do this in any case
>
>> take advantage on the EdgeNGramFilter placed in the new search field
> Something like
> http://lucidworks.com/blog/auto-suggest-from-popular-queries-using-edg
> engrams/ but searching the copy-field (and the filter field(s)) 
> instead of the separate index?
> But then, wouldn't I be getting the complete content of the copyfield, 
> instead of a single word, as a "result"?
>
>
> -Ursprüngliche Nachricht-
> Von: Jorge Luis Betancourt González [mailto:jlbetanco...@uci.cu]
> Gesendet: Samstag, 25. Oktober 2014 17:30
> An: solr-user@lucene.apache.org
> Betreff: Re: AW: (auto)suggestions, but ony from a "filtered" set of 
> documents
>
> Maybe you could use copyField to populate one field with the values (fields) 
> that you like to use for suggestions, then you could search only on this 
> field and filter by any other field in your schema, and take advantage on the 
> EdgeNGramFilter placed in the new search field.
>
> Regards,
>
> - Original Message -
> From: "Clemens Wyss DEV" 
> To: solr-user@lucene.apache.org
> Sent: Saturday, October 25, 2014 2:43:46 AM
> Subject: AW: (auto)suggestions, but ony from a "filtered" set of 
> documents
>
> Possibly making use of FilterAtomicReader?
> http://lucene.apache.org/core/4_7_0/core/org/apache/lucene/index/Filte
> rAtomicReader.html
>
> -Ursprüngliche Nachricht-
> Von: Clemens Wyss DEV [mailto:clemens...@mysign.ch]
> Gesendet: Freitag, 24. Oktober 2014 18:31
> An: solr-user@lucene.apache.org
> Betreff: AW: (auto)suggestions, but ony from a "filtered" set of 
> documents
>
> If possible I'd like to omit the sparate core. We have this approach in the 
> current Lucene-only-solution. The main drawback IMHO is, that whenever the 
> main index chnages you need to completely reindex the term-index.
> Is it at all possible to write an own Suggester, which could do what I 
> want/need?
>
> -Ursprüngliche Nachricht-
> Von: Jorge Luis Betancourt Gonzalez [mailto:jlbetanco...@uci.cu]
> Gesendet: Freitag, 26. September 2014 19:15
> An: solr-user@lucene.apache.org
> Betreff: Re: (auto)suggestions, but ony from a "filtered" set of 
> documents
>
> Perhaps instead of the suggester component you could use the EdgeNGramFilter 
> and provide partial matches so you will me able to configure a custom request 
> handler that will "suggest" terms of phrases for you. I'm using this approach 
> to provide queries suggestions, of course I'm indexing the queries into a 
> separated core.
>
> Greetings,
>
> On Sep 26, 2014, at 8:49 AM, Clemens Wyss DEV  wrote:
>
>> Either my intention is dumb (pls let me know ;)), or there is no answer to 
>> this problem. If so, I will have to index my sources into separate cores.
>> But then the questions arise:
>> a) how do I get suggestions from more than one core? Multiple 
>> suggest-requests, then merge?
>> b) how doe I get (ranked) results from more than one core?
>> In Lucene I was able to use a MultiIndexReader (one IndexReaders per 
>> index)
>>
>> -Ursprüngliche Nachricht-
>> Von: Clemens Wyss DEV [mailto:clemens...@mysign.ch]
>> Gesendet: Donnerstag, 25. September 2014 10:24
>> An: solr-user@lucene.apache.org
>> Betreff: (auto)suggestions, but ony from a "filtered" set of 
>> documents
>>
>> What I'd like to do is
>> http://localhost:8983/solr/solrpedia/suggest?q=atm&qf=source:> e>
>>
>> Through qf (or however the parameter

how to query this?

[rulinma]

I have a query on course:
1. if course will begin, then sort those by beginTime asc.
2. if couse ended, then sort those by begin desc.

how to query use solr?

thanks.




--
View this message in context: 
http://lucene.472066.n3.nabble.com/how-to-query-this-tp4165998.html
Sent from the Solr - User mailing list archive at Nabble.com.

RE: OpenExchangeRates.Org rates in solr

[Will Martin]

Cool. After I wrote it occurred to me that the exchange rates API might make 
for a very useful contrib/  component.

Good luck.

-Original Message-
From: Olivier Austina [mailto:olivier.aust...@gmail.com] 
Sent: Sunday, October 26, 2014 3:11 PM
To: solr-user@lucene.apache.org
Subject: Re: OpenExchangeRates.Org rates in solr

Hi Will,

I am learning Solr now. I can use it  later for business or for free access. 
Thank you.

Regards
Olivier


2014-10-26 17:32 GMT+01:00 Will Martin :

> Hi Olivier:
>
> Can you clarify this message? Are you using Solr at the business? Or 
> are you giving free access to solr installations?
>
> Thanks,
> Will
>
>
> -Original Message-
> From: Olivier Austina [mailto:olivier.aust...@gmail.com]
> Sent: Sunday, October 26, 2014 10:57 AM
> To: solr-user@lucene.apache.org
> Subject: OpenExchangeRates.Org rates in solr
>
> Hi,
>
> There is a way to see the OpenExchangeRates.Org < 
> http://www.OpenExchangeRates.Org> rates used in Solr somewhere. I have 
> changed the configuration to use these rates. Thank you.
> Regards
> Olivier
>
>

Heavy Multi-threaded indexing and SolrCloud 4.10.1 replicas out of synch.

[S.L]

Folks,

I have posted previously about this , I am using SolrCloud 4.10.1 and have
a sharded collection with  6 nodes , 3 shards and a replication factor of 2.

I am indexing Solr using a Hadoop job , I have 15 Map fetch tasks , that
can each have upto 5 threds each , so the load on the indexing side can get
to as high as 75 concurrent threads.

I am facing an issue where the replicas of a particular shard(s) are
consistently getting out of synch , initially I thought this was beccause I
was using a custom component , but I did a fresh install and removed the
custom component and reindexed using the Hadoop job , I still see the same
behavior.

I do not see any exceptions in my catalina.out , like OOM , or any other
excepitions, I suspecting thi scould be because of the multi-threaded
indexing nature of the Hadoop job . I use CloudSolrServer from my java code
to index and initialize the CloudSolrServer using a 3 node ZK ensemble.

Does any one know of any known issues with a highly multi-threaded indexing
and SolrCloud ?

Can someone help ? This issue has been slowing things down on my end for a
while now.

Thanks and much appreciated!

Re: AW: AW: (auto)suggestions, but ony from a "filtered" set of documents

[Michael Sokolov]

This project (https://github.com/safarijv/ifpress-solr-plugin/) has some 
examples of custom Solr UpdateRequestProcessors that feed a single 
suggester from multiple fields, applying different weights to them, 
using complete values from some and analyzing others into tokens.


The first thing I did was FieldMergingProcessor, which creates a new 
field, kind of like copyfield, but allowing for some 
analysis/transformation to be done just prior to copying the field values.


I think a better solution is MultiSuggesterProcessor and friends, which 
multiplexes different input fields to a single suggester. It also 
manages NRT updates to AnalyzingInfixSuggester


I haven't had a chance to up good docs or generalize very much, but if 
you have questions feel free to get in touch.


-Mike

On 10/26/14 3:52 AM, Clemens Wyss DEV wrote:

Maybe you could use copyField to populate one field with the values
(fields) that you like to use for suggestions

We intended to do this in any case


take advantage on the EdgeNGramFilter placed in the new search field

Something like
http://lucidworks.com/blog/auto-suggest-from-popular-queries-using-edgengrams/
but searching the copy-field (and the filter field(s)) instead of the separate 
index?
But then, wouldn't I be getting the complete content of the copyfield, instead of a 
single word, as a "result"?


-Ursprüngliche Nachricht-
Von: Jorge Luis Betancourt González [mailto:jlbetanco...@uci.cu]
Gesendet: Samstag, 25. Oktober 2014 17:30
An: solr-user@lucene.apache.org
Betreff: Re: AW: (auto)suggestions, but ony from a "filtered" set of documents

Maybe you could use copyField to populate one field with the values (fields) 
that you like to use for suggestions, then you could search only on this field 
and filter by any other field in your schema, and take advantage on the 
EdgeNGramFilter placed in the new search field.

Regards,

- Original Message -
From: "Clemens Wyss DEV" 
To: solr-user@lucene.apache.org
Sent: Saturday, October 25, 2014 2:43:46 AM
Subject: AW: (auto)suggestions, but ony from a "filtered" set of documents

Possibly making use of FilterAtomicReader?
http://lucene.apache.org/core/4_7_0/core/org/apache/lucene/index/FilterAtomicReader.html

-Ursprüngliche Nachricht-
Von: Clemens Wyss DEV [mailto:clemens...@mysign.ch]
Gesendet: Freitag, 24. Oktober 2014 18:31
An: solr-user@lucene.apache.org
Betreff: AW: (auto)suggestions, but ony from a "filtered" set of documents

If possible I'd like to omit the sparate core. We have this approach in the 
current Lucene-only-solution. The main drawback IMHO is, that whenever the main 
index chnages you need to completely reindex the term-index.
Is it at all possible to write an own Suggester, which could do what I 
want/need?

-Ursprüngliche Nachricht-
Von: Jorge Luis Betancourt Gonzalez [mailto:jlbetanco...@uci.cu]
Gesendet: Freitag, 26. September 2014 19:15
An: solr-user@lucene.apache.org
Betreff: Re: (auto)suggestions, but ony from a "filtered" set of documents

Perhaps instead of the suggester component you could use the EdgeNGramFilter and provide 
partial matches so you will me able to configure a custom request handler that will 
"suggest" terms of phrases for you. I'm using this approach to provide queries 
suggestions, of course I'm indexing the queries into a separated core.

Greetings,

On Sep 26, 2014, at 8:49 AM, Clemens Wyss DEV  wrote:


Either my intention is dumb (pls let me know ;)), or there is no answer to this 
problem. If so, I will have to index my sources into separate cores.
But then the questions arise:
a) how do I get suggestions from more than one core? Multiple suggest-requests, 
then merge?
b) how doe I get (ranked) results from more than one core?
In Lucene I was able to use a MultiIndexReader (one IndexReaders per index)

-Ursprüngliche Nachricht-
Von: Clemens Wyss DEV [mailto:clemens...@mysign.ch]
Gesendet: Donnerstag, 25. September 2014 10:24
An: solr-user@lucene.apache.org
Betreff: (auto)suggestions, but ony from a "filtered" set of documents

What I'd like to do is
http://localhost:8983/solr/solrpedia/suggest?q=atm&qf=source:

Through qf (or however the parameter shall be called) I'd like to restrict the 
suggestions to documents which fit the given qf-query.
I need this filter if (as posted in a previous thread) I intend to put "different 
kind of data" into one core/collection, cause suggestion shall be restrictable to 
one or many source(s)

Concurso "Mi selfie por los 5". Detalles en 
http://justiciaparaloscinco.wordpress.com

Re: OpenExchangeRates.Org rates in solr

[Olivier Austina]

Hi Will,

I am learning Solr now. I can use it  later for business or for free
access. Thank you.

Regards
Olivier


2014-10-26 17:32 GMT+01:00 Will Martin :

> Hi Olivier:
>
> Can you clarify this message? Are you using Solr at the business? Or are
> you giving free access to solr installations?
>
> Thanks,
> Will
>
>
> -Original Message-
> From: Olivier Austina [mailto:olivier.aust...@gmail.com]
> Sent: Sunday, October 26, 2014 10:57 AM
> To: solr-user@lucene.apache.org
> Subject: OpenExchangeRates.Org rates in solr
>
> Hi,
>
> There is a way to see the OpenExchangeRates.Org <
> http://www.OpenExchangeRates.Org> rates used in Solr somewhere. I have
> changed the configuration to use these rates. Thank you.
> Regards
> Olivier
>
>

RE: OpenExchangeRates.Org rates in solr

[Will Martin]

Hi Olivier:

Can you clarify this message? Are you using Solr at the business? Or are you 
giving free access to solr installations?

Thanks,
Will


-Original Message-
From: Olivier Austina [mailto:olivier.aust...@gmail.com] 
Sent: Sunday, October 26, 2014 10:57 AM
To: solr-user@lucene.apache.org
Subject: OpenExchangeRates.Org rates in solr

Hi,

There is a way to see the OpenExchangeRates.Org 
 rates used in Solr somewhere. I have changed 
the configuration to use these rates. Thank you.
Regards
Olivier

Re: suggestion for new custom atomic update

[Alexandre Rafalovitch]

I am not sure what the problem is. URP catches all operations. So, you
can modify the source document to add the calculation when the field_a
is either new or updated.

Or are you trying to calculate things across multiple documents? In
that case, neither mine nor your solution will work, I think.

Regards,
   Alex.
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resources and newsletter: http://www.solr-start.com/ and @solrstart
Solr popularizers community: https://www.linkedin.com/groups?gid=6713853


On 26 October 2014 12:00, Elran Dvir  wrote:
> Thanks for your response.
>
> If the calculation is based on the most recent summed value of field_a and 
> the value of field_a in the update, how can I?
>
> Thanks.
>
> -Original Message-
> From: Alexandre Rafalovitch [mailto:arafa...@gmail.com]
> Sent: Sunday, October 26, 2014 2:11 PM
> To: solr-user
> Subject: RE: suggestion for new custom atomic update
>
> Can't you do the calculation in custom UpdateRequestProcessor?
>
> Regards,
> Alex
> On 26/10/2014 4:17 am, "Elran Dvir"  wrote:
>
>> Hi all,
>>
>> Did anyone have a chance to review my idea?
>>
>> Thanks.
>>
>> -Original Message-
>> From: Elran Dvir
>> Sent: Monday, October 20, 2014 12:42 PM
>> To: solr-user
>> Subject: suggestion for new custom atomic update
>>
>> Hi all,
>>
>> This is my use  case:
>> I have a stored field, field_a, which is atomic updated (let's say by
>> "inc"). field_a is stored but not indexed due to the large number of
>> distinct values it can have.
>> I need to index field_b (I need facet and stats on it) which is not in
>> the document but its value is based on a calculation of the recent (e.g.
>> summed) value of field_a.
>> There is no way to do it nowadays.
>> So I thought of a new method: custom atomic update.
>>
>> There will be a new interface in Solr:
>>
>> public interface CustomAtomicUpdater {
>> public void update(SolrInputDocument oldDoc, String fieldName,
>> Object
>> fieldVal) ;  }
>>
>> There will be a new attribute for fields in schema.xml called
>> "customAtomicUpdateClass" (and all support in code, of course).
>> The value is a class which is an implementation of  CustomAtomicUpdater.
>> In our example it will be defined for field_a.
>>
>> In method "getUpdatedDocument" in DistributedUpdateProcessor.java, we
>> will add handling of "custom" case:
>>
>>} else if ("custom".equals(key)) {
>> updateField = true;
>> SchemaField sf = schema.getField(sif.getName());
>> String customAtomicUpdaterClassName =
>> sf.getCustomAtomicUpdaterClass();
>> if (customAtomicUpdaterClassName == null) {
>>   throw new SolrException(ErrorCode.BAD_REQUEST, "There is
>> no customAtomicUpdaterClass defined for " + sif + ".");
>> }
>> CustomAtomicUpdater updater = schema.getResourceLoader()
>> .newInstance(customAtomicUpdaterClassName,
>> CustomAtomicUpdater.class);
>> if (updater == null) {
>>   throw new SolrException(ErrorCode.BAD_REQUEST, "Was
>> unable to create instance of " + customAtomicUpdaterClassName + ".");
>> }
>> updater.update(oldDoc, sif.getName(), fieldVal);
>>
>>   }
>>
>> In my implementation I will sum field_a (oldvalue + newvalue) and
>> update field_b according to my logic.
>>
>> Example of use:
>> 
>>   
>> 128
>>   
>> 
>>
>> What do say about my suggestion?
>>
>> Thanks.
>>
>
>
> Email secured by Check Point

RE: suggestion for new custom atomic update

[Elran Dvir]

Thanks for your response.

If the calculation is based on the most recent summed value of field_a and the 
value of field_a in the update, how can I?

Thanks.

-Original Message-
From: Alexandre Rafalovitch [mailto:arafa...@gmail.com] 
Sent: Sunday, October 26, 2014 2:11 PM
To: solr-user
Subject: RE: suggestion for new custom atomic update

Can't you do the calculation in custom UpdateRequestProcessor?

Regards,
Alex
On 26/10/2014 4:17 am, "Elran Dvir"  wrote:

> Hi all,
>
> Did anyone have a chance to review my idea?
>
> Thanks.
>
> -Original Message-
> From: Elran Dvir
> Sent: Monday, October 20, 2014 12:42 PM
> To: solr-user
> Subject: suggestion for new custom atomic update
>
> Hi all,
>
> This is my use  case:
> I have a stored field, field_a, which is atomic updated (let's say by 
> "inc"). field_a is stored but not indexed due to the large number of 
> distinct values it can have.
> I need to index field_b (I need facet and stats on it) which is not in 
> the document but its value is based on a calculation of the recent (e.g.
> summed) value of field_a.
> There is no way to do it nowadays.
> So I thought of a new method: custom atomic update.
>
> There will be a new interface in Solr:
>
> public interface CustomAtomicUpdater {
> public void update(SolrInputDocument oldDoc, String fieldName, 
> Object
> fieldVal) ;  }
>
> There will be a new attribute for fields in schema.xml called 
> "customAtomicUpdateClass" (and all support in code, of course).
> The value is a class which is an implementation of  CustomAtomicUpdater.
> In our example it will be defined for field_a.
>
> In method "getUpdatedDocument" in DistributedUpdateProcessor.java, we 
> will add handling of "custom" case:
>
>} else if ("custom".equals(key)) {
> updateField = true;
> SchemaField sf = schema.getField(sif.getName());
> String customAtomicUpdaterClassName = 
> sf.getCustomAtomicUpdaterClass();
> if (customAtomicUpdaterClassName == null) {
>   throw new SolrException(ErrorCode.BAD_REQUEST, "There is 
> no customAtomicUpdaterClass defined for " + sif + ".");
> }
> CustomAtomicUpdater updater = schema.getResourceLoader()
> .newInstance(customAtomicUpdaterClassName,
> CustomAtomicUpdater.class);
> if (updater == null) {
>   throw new SolrException(ErrorCode.BAD_REQUEST, "Was 
> unable to create instance of " + customAtomicUpdaterClassName + ".");
> }
> updater.update(oldDoc, sif.getName(), fieldVal);
>
>   }
>
> In my implementation I will sum field_a (oldvalue + newvalue) and 
> update field_b according to my logic.
>
> Example of use:
> 
>   
> 128
>   
> 
>
> What do say about my suggestion?
>
> Thanks.
>


Email secured by Check Point

OpenExchangeRates.Org rates in solr

[Olivier Austina]

Hi,

There is a way to see the OpenExchangeRates.Org
 rates used in Solr somewhere. I have
changed the configuration to use these rates. Thank you.
Regards
Olivier

RE: suggestion for new custom atomic update

[Alexandre Rafalovitch]

Can't you do the calculation in custom UpdateRequestProcessor?

Regards,
Alex
On 26/10/2014 4:17 am, "Elran Dvir"  wrote:

> Hi all,
>
> Did anyone have a chance to review my idea?
>
> Thanks.
>
> -Original Message-
> From: Elran Dvir
> Sent: Monday, October 20, 2014 12:42 PM
> To: solr-user
> Subject: suggestion for new custom atomic update
>
> Hi all,
>
> This is my use  case:
> I have a stored field, field_a, which is atomic updated (let's say by
> "inc"). field_a is stored but not indexed due to the large number of
> distinct values it can have.
> I need to index field_b (I need facet and stats on it) which is not in the
> document but its value is based on a calculation of the recent (e.g.
> summed) value of field_a.
> There is no way to do it nowadays.
> So I thought of a new method: custom atomic update.
>
> There will be a new interface in Solr:
>
> public interface CustomAtomicUpdater {
> public void update(SolrInputDocument oldDoc, String fieldName, Object
> fieldVal) ;  }
>
> There will be a new attribute for fields in schema.xml called
> "customAtomicUpdateClass" (and all support in code, of course).
> The value is a class which is an implementation of  CustomAtomicUpdater.
> In our example it will be defined for field_a.
>
> In method "getUpdatedDocument" in DistributedUpdateProcessor.java, we will
> add handling of "custom" case:
>
>} else if ("custom".equals(key)) {
> updateField = true;
> SchemaField sf = schema.getField(sif.getName());
> String customAtomicUpdaterClassName =
> sf.getCustomAtomicUpdaterClass();
> if (customAtomicUpdaterClassName == null) {
>   throw new SolrException(ErrorCode.BAD_REQUEST, "There is no
> customAtomicUpdaterClass defined for " + sif + ".");
> }
> CustomAtomicUpdater updater = schema.getResourceLoader()
> .newInstance(customAtomicUpdaterClassName,
> CustomAtomicUpdater.class);
> if (updater == null) {
>   throw new SolrException(ErrorCode.BAD_REQUEST, "Was unable
> to create instance of " + customAtomicUpdaterClassName + ".");
> }
> updater.update(oldDoc, sif.getName(), fieldVal);
>
>   }
>
> In my implementation I will sum field_a (oldvalue + newvalue) and update
> field_b according to my logic.
>
> Example of use:
> 
>   
> 128
>   
> 
>
> What do say about my suggestion?
>
> Thanks.
>

RE: suggestion for new custom atomic update

[Elran Dvir]

Hi all,

Did anyone have a chance to review my idea?

Thanks.

-Original Message-
From: Elran Dvir 
Sent: Monday, October 20, 2014 12:42 PM
To: solr-user
Subject: suggestion for new custom atomic update

Hi all,

This is my use  case:
I have a stored field, field_a, which is atomic updated (let's say by "inc"). 
field_a is stored but not indexed due to the large number of distinct values it 
can have.
I need to index field_b (I need facet and stats on it) which is not in the 
document but its value is based on a calculation of the recent (e.g. summed) 
value of field_a.
There is no way to do it nowadays.
So I thought of a new method: custom atomic update.

There will be a new interface in Solr:

public interface CustomAtomicUpdater {
public void update(SolrInputDocument oldDoc, String fieldName, Object 
fieldVal) ;  }

There will be a new attribute for fields in schema.xml called 
"customAtomicUpdateClass" (and all support in code, of course). 
The value is a class which is an implementation of  CustomAtomicUpdater.
In our example it will be defined for field_a.

In method "getUpdatedDocument" in DistributedUpdateProcessor.java, we will add 
handling of "custom" case:

   } else if ("custom".equals(key)) {
updateField = true;
SchemaField sf = schema.getField(sif.getName());
String customAtomicUpdaterClassName = 
sf.getCustomAtomicUpdaterClass();
if (customAtomicUpdaterClassName == null) {
  throw new SolrException(ErrorCode.BAD_REQUEST, "There is no 
customAtomicUpdaterClass defined for " + sif + ".");
}
CustomAtomicUpdater updater = schema.getResourceLoader()
.newInstance(customAtomicUpdaterClassName, 
CustomAtomicUpdater.class);
if (updater == null) {
  throw new SolrException(ErrorCode.BAD_REQUEST, "Was unable to 
create instance of " + customAtomicUpdaterClassName + ".");
}
updater.update(oldDoc, sif.getName(), fieldVal);
  
  }

In my implementation I will sum field_a (oldvalue + newvalue) and update 
field_b according to my logic.

Example of use:

  
128
  


What do say about my suggestion?

Thanks.

AW: AW: (auto)suggestions, but ony from a "filtered" set of documents

[Clemens Wyss DEV]

> Maybe you could use copyField to populate one field with the values 
>(fields) that you like to use for suggestions
We intended to do this in any case

> take advantage on the EdgeNGramFilter placed in the new search field
Something like 
http://lucidworks.com/blog/auto-suggest-from-popular-queries-using-edgengrams/
but searching the copy-field (and the filter field(s)) instead of the separate 
index? 
But then, wouldn't I be getting the complete content of the copyfield, instead 
of a single word, as a "result"?


-Ursprüngliche Nachricht-
Von: Jorge Luis Betancourt González [mailto:jlbetanco...@uci.cu] 
Gesendet: Samstag, 25. Oktober 2014 17:30
An: solr-user@lucene.apache.org
Betreff: Re: AW: (auto)suggestions, but ony from a "filtered" set of documents

Maybe you could use copyField to populate one field with the values (fields) 
that you like to use for suggestions, then you could search only on this field 
and filter by any other field in your schema, and take advantage on the 
EdgeNGramFilter placed in the new search field.

Regards,

- Original Message -
From: "Clemens Wyss DEV" 
To: solr-user@lucene.apache.org
Sent: Saturday, October 25, 2014 2:43:46 AM
Subject: AW: (auto)suggestions, but ony from a "filtered" set of documents

Possibly making use of FilterAtomicReader?
http://lucene.apache.org/core/4_7_0/core/org/apache/lucene/index/FilterAtomicReader.html
 

-Ursprüngliche Nachricht-
Von: Clemens Wyss DEV [mailto:clemens...@mysign.ch] 
Gesendet: Freitag, 24. Oktober 2014 18:31
An: solr-user@lucene.apache.org
Betreff: AW: (auto)suggestions, but ony from a "filtered" set of documents

If possible I'd like to omit the sparate core. We have this approach in the 
current Lucene-only-solution. The main drawback IMHO is, that whenever the main 
index chnages you need to completely reindex the term-index.
Is it at all possible to write an own Suggester, which could do what I 
want/need? 

-Ursprüngliche Nachricht-
Von: Jorge Luis Betancourt Gonzalez [mailto:jlbetanco...@uci.cu] 
Gesendet: Freitag, 26. September 2014 19:15
An: solr-user@lucene.apache.org
Betreff: Re: (auto)suggestions, but ony from a "filtered" set of documents

Perhaps instead of the suggester component you could use the EdgeNGramFilter 
and provide partial matches so you will me able to configure a custom request 
handler that will "suggest" terms of phrases for you. I'm using this approach 
to provide queries suggestions, of course I'm indexing the queries into a 
separated core. 

Greetings,

On Sep 26, 2014, at 8:49 AM, Clemens Wyss DEV  wrote:

> Either my intention is dumb (pls let me know ;)), or there is no answer to 
> this problem. If so, I will have to index my sources into separate cores. 
> But then the questions arise:
> a) how do I get suggestions from more than one core? Multiple 
> suggest-requests, then merge?
> b) how doe I get (ranked) results from more than one core?
> In Lucene I was able to use a MultiIndexReader (one IndexReaders per index)
> 
> -Ursprüngliche Nachricht-
> Von: Clemens Wyss DEV [mailto:clemens...@mysign.ch] 
> Gesendet: Donnerstag, 25. September 2014 10:24
> An: solr-user@lucene.apache.org
> Betreff: (auto)suggestions, but ony from a "filtered" set of documents
> 
> What I'd like to do is
> http://localhost:8983/solr/solrpedia/suggest?q=atm&qf=source:
> 
> Through qf (or however the parameter shall be called) I'd like to restrict 
> the suggestions to documents which fit the given qf-query. 
> I need this filter if (as posted in a previous thread) I intend to put 
> "different kind of data" into one core/collection, cause suggestion shall be 
> restrictable to one or many source(s)

Concurso "Mi selfie por los 5". Detalles en 
http://justiciaparaloscinco.wordpress.com