Re: Unrelated Features within Data at Solr
Can you have a custom UpdateRequestProcessor in the chain that just skips processing such requests? Regards, Alex. Personal website: http://www.outerthoughts.com/ Current project: http://www.solr-start.com/ - Accelerating your Solr proficiency On Thu, May 22, 2014 at 6:34 PM, Furkan KAMACI furkankam...@gmail.com wrote: Hi; As you know that commitWithin is a nice feature for Solr. You can either use it via URL as a query parameter or within documents to index. As like: {add:{ doc:{id:change.me,title:change.me},boost:1.0,overwrite:true,commitWithin:1000}} However I think that is is not a feature of data and it should not be permitted within data to index. I have a use case for it: I have designed an infrastructure that drops url parameters that is not related to data (as like commit or commitWithin). However as Solr supports a non-data related feature within data as a meta data I could not drop it and I have to analyze all data or customize Solr. What do you think about that? Does it a good design to allow something like that within data as meta data? Thanks; Furkan KAMACI - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Unrelated Features within Data at Solr
By the way, I think that I can drop that parameter within a custom UpdateRequestProcessor? 2014-05-22 17:32 GMT+03:00 Furkan KAMACI furkankam...@gmail.com: Hi Alexandre; Actually I do not want to skip them. I just want to drop commitWithin parameter. It seems that I have to customize Solr for it. I think that it would be nice if commitWithin had been only query parameter instead of sending such kind of information within data too. Thanks; Furkan KAMACI 2014-05-22 17:02 GMT+03:00 Alexandre Rafalovitch arafa...@gmail.com: Can you have a custom UpdateRequestProcessor in the chain that just skips processing such requests? Regards, Alex. Personal website: http://www.outerthoughts.com/ Current project: http://www.solr-start.com/ - Accelerating your Solr proficiency On Thu, May 22, 2014 at 6:34 PM, Furkan KAMACI furkankam...@gmail.com wrote: Hi; As you know that commitWithin is a nice feature for Solr. You can either use it via URL as a query parameter or within documents to index. As like: {add:{ doc:{id:change.me,title:change.me },boost:1.0,overwrite:true,commitWithin:1000}} However I think that is is not a feature of data and it should not be permitted within data to index. I have a use case for it: I have designed an infrastructure that drops url parameters that is not related to data (as like commit or commitWithin). However as Solr supports a non-data related feature within data as a meta data I could not drop it and I have to analyze all data or customize Solr. What do you think about that? Does it a good design to allow something like that within data as meta data? Thanks; Furkan KAMACI - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Unrelated Features within Data at Solr
Hi Alexandre; Actually I do not want to skip them. I just want to drop commitWithin parameter. It seems that I have to customize Solr for it. I think that it would be nice if commitWithin had been only query parameter instead of sending such kind of information within data too. Thanks; Furkan KAMACI 2014-05-22 17:02 GMT+03:00 Alexandre Rafalovitch arafa...@gmail.com: Can you have a custom UpdateRequestProcessor in the chain that just skips processing such requests? Regards, Alex. Personal website: http://www.outerthoughts.com/ Current project: http://www.solr-start.com/ - Accelerating your Solr proficiency On Thu, May 22, 2014 at 6:34 PM, Furkan KAMACI furkankam...@gmail.com wrote: Hi; As you know that commitWithin is a nice feature for Solr. You can either use it via URL as a query parameter or within documents to index. As like: {add:{ doc:{id:change.me,title:change.me },boost:1.0,overwrite:true,commitWithin:1000}} However I think that is is not a feature of data and it should not be permitted within data to index. I have a use case for it: I have designed an infrastructure that drops url parameters that is not related to data (as like commit or commitWithin). However as Solr supports a non-data related feature within data as a meta data I could not drop it and I have to analyze all data or customize Solr. What do you think about that? Does it a good design to allow something like that within data as meta data? Thanks; Furkan KAMACI - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Unrelated Features within Data at Solr
To be clear, the commitWithin parameter is not within the “data” – an update stream consists of a sequence of “commands”, such as “add”, “delete”, “commit”, and “optimize”, while the “data” is contained within a “doc” element. The “commitWithin” parameter is specified for the “command”, not the “data”/”doc”. -- Jack Krupansky From: Furkan KAMACI Sent: Thursday, May 22, 2014 10:32 AM To: dev@lucene.apache.org Subject: Re: Unrelated Features within Data at Solr Hi Alexandre; Actually I do not want to skip them. I just want to drop commitWithin parameter. It seems that I have to customize Solr for it. I think that it would be nice if commitWithin had been only query parameter instead of sending such kind of information within data too. Thanks; Furkan KAMACI 2014-05-22 17:02 GMT+03:00 Alexandre Rafalovitch arafa...@gmail.com: Can you have a custom UpdateRequestProcessor in the chain that just skips processing such requests? Regards, Alex. Personal website: http://www.outerthoughts.com/ Current project: http://www.solr-start.com/ - Accelerating your Solr proficiency On Thu, May 22, 2014 at 6:34 PM, Furkan KAMACI furkankam...@gmail.com wrote: Hi; As you know that commitWithin is a nice feature for Solr. You can either use it via URL as a query parameter or within documents to index. As like: {add:{ doc:{id:change.me,title:change.me},boost:1.0,overwrite:true,commitWithin:1000}} However I think that is is not a feature of data and it should not be permitted within data to index. I have a use case for it: I have designed an infrastructure that drops url parameters that is not related to data (as like commit or commitWithin). However as Solr supports a non-data related feature within data as a meta data I could not drop it and I have to analyze all data or customize Solr. What do you think about that? Does it a good design to allow something like that within data as meta data? Thanks; Furkan KAMACI - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org