[jira] [Updated] (SOLR-2280) commitWithin ignored for a delete query
[ https://issues.apache.org/jira/browse/SOLR-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Grande updated SOLR-2280: -- Attachment: SOLR-2280.patch I'm submitting a patch that implements commitWithin on deletes. The patch is for the 3x branch. Two things should be noted: # The commit is fired even if the delete doesn't really delete any document. # When using the BinaryUpdateRequestHandler the params of the UpdateRequest are loaded when parsing the docs. If the request doesn't include a docs list, then the params aren't loaded. I added a workaround for this, but SOLR-1164 should solve this problem definitely. > commitWithin ignored for a delete query > --- > > Key: SOLR-2280 > URL: https://issues.apache.org/jira/browse/SOLR-2280 > Project: Solr > Issue Type: Bug > Components: clients - java >Reporter: David Smiley >Priority: Minor > Fix For: 3.4, 4.0 > > Attachments: SOLR-2280.patch > > > The commitWithin option on an UpdateRequest is only honored for requests > containing new documents. It does not, for example, work with a delete > query. The following doesn't work as expected: > {code:java} > UpdateRequest request = new UpdateRequest(); > request.deleteById("id123"); > request.setCommitWithin(1000); > solrServer.request(request); > {code} > In my opinion, the commitWithin attribute should be permitted on the > xml tag as well as . Such a change would go in > XMLLoader.java and its would have some ramifications elsewhere too. Once > this is done, then UpdateRequest.getXml() can be updated to generate the > right XML. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-1085) SolrJ client java does not support moreLikeThis querys and results
[ https://issues.apache.org/jira/browse/SOLR-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Grande updated SOLR-1085: -- Attachment: SOLR-1085.patch Attached is a patch that adds MoreLikeThis support to SolrJ. The patch is for the trunk, but if necessary I can backport it to the 3x branch. > SolrJ client java does not support moreLikeThis querys and results > -- > > Key: SOLR-1085 > URL: https://issues.apache.org/jira/browse/SOLR-1085 > Project: Solr > Issue Type: Improvement > Components: clients - java > Environment: SolrJ java client >Reporter: Maurice Jumelet > Fix For: 3.4, 4.0 > > Attachments: SOLR-1085.patch, solrj-java-morelikethis.patch > > > Although SOLR supports the more like this querys (see > http://wiki.apache.org/solr/MoreLikeThis) these type of query are currently > not supported by the SOLR java client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Updated: (LUCENE-2482) Index sorter
[ https://issues.apache.org/jira/browse/LUCENE-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Grande updated LUCENE-2482: Attachment: LUCENE-2482-4.0.patch Hi! I'm attaching a patch with an implementation of this feature for Lucene 4.0. I'm not sure if the style is right because I can't download the codestyle.xml file for Eclipse. > Index sorter > > > Key: LUCENE-2482 > URL: https://issues.apache.org/jira/browse/LUCENE-2482 > Project: Lucene - Java > Issue Type: New Feature > Components: contrib/* >Affects Versions: 3.1, 4.0 >Reporter: Andrzej Bialecki >Assignee: Andrzej Bialecki > Fix For: 3.1, 4.0 > > Attachments: indexSorter.patch, LUCENE-2482-4.0.patch > > > A tool to sort index according to a float document weight. Documents with > high weight are given low document numbers, which means that they will be > first evaluated. When using a strategy of "early termination" of queries (see > TimeLimitedCollector) such sorting significantly improves the quality of > partial results. > (Originally this tool was created by Doug Cutting in Nutch, and used norms as > document weights - thus the ordering was limited by the limited resolution of > norms. This is a pure Lucene version of the tool, and it uses arbitrary > floats from a specified stored field). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org