[jira] Created: (SOLR-763) Support for LUCENE-1380 :: ShingleFilter.coterminalPositionIncrement
Support for LUCENE-1380 :: ShingleFilter.coterminalPositionIncrement Key: SOLR-763 URL: https://issues.apache.org/jira/browse/SOLR-763 Project: Solr Issue Type: Improvement Reporter: Michael Semb Wever Fix For: 1.4 Patch so that ShingleFilterFactory can deserialise the coterminalPositionIncrement property. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-763) Support for LUCENE-1380 :: ShingleFilter.coterminalPositionIncrement
[ https://issues.apache.org/jira/browse/SOLR-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated SOLR-763: Attachment: SOLR-763.patch Patch to support new property coterminalPositionIncrement that appears in LUCENE-1380 Support for LUCENE-1380 :: ShingleFilter.coterminalPositionIncrement Key: SOLR-763 URL: https://issues.apache.org/jira/browse/SOLR-763 Project: Solr Issue Type: Improvement Reporter: Michael Semb Wever Fix For: 1.4 Attachments: SOLR-763.patch Patch so that ShingleFilterFactory can deserialise the coterminalPositionIncrement property. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
log number of hits returned
I just noticed that the hits parameter that gets logged seems to be returning the number of documents actually returned, not the number of documents that matched the query + filters. Should it? num docs returned can be derived from num docs matched and offset,rows, but not vice-versa. -Yonik
Re: log number of hits returned
Ouch yes, it definitely should log the total number hits, not the number of documents returned. Erik On Sep 10, 2008, at 12:19 PM, Yonik Seeley wrote: I just noticed that the hits parameter that gets logged seems to be returning the number of documents actually returned, not the number of documents that matched the query + filters. Should it? num docs returned can be derived from num docs matched and offset,rows, but not vice-versa. -Yonik
[jira] Created: (SOLR-764) facet.limit=-1 with facet.sort=false does not work in distributed search
facet.limit=-1 with facet.sort=false does not work in distributed search Key: SOLR-764 URL: https://issues.apache.org/jira/browse/SOLR-764 Project: Solr Issue Type: New Feature Affects Versions: 1.3 Reporter: Wojtek Piaseczny Fix For: 1.4 If you specify facet.limit=-1 and facet.sort=false, no facet results are returned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-764) facet.limit=-1 with facet.sort=false does not work in distributed search
[ https://issues.apache.org/jira/browse/SOLR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629874#action_12629874 ] Amit Nithian commented on SOLR-764: --- Are you purposely trying to disable facet results? Why not simply pass in facet=false parameter? facet.limit=-1 with facet.sort=false does not work in distributed search Key: SOLR-764 URL: https://issues.apache.org/jira/browse/SOLR-764 Project: Solr Issue Type: New Feature Affects Versions: 1.3 Reporter: Wojtek Piaseczny Fix For: 1.4 If you specify facet.limit=-1 and facet.sort=false, no facet results are returned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: 1.3.0 Candidate
So, how we doing on the Woodstox stuff? Have people had a chance to try it out on trunk? If so, can we port to the 1.3 branch? On Sep 9, 2008, at 9:19 AM, Grant Ingersoll wrote: On Sep 7, 2008, at 8:59 PM, Chris Hostetter wrote: (Curiousity: Grant, is the hudson config for doing releases not working out? it seemed like a really sweet way to automate everything and i'm just wondering if you found something that made it not worthwhile ... it seems to be gone now) FWIW, I added a prepare-release target to the build, that I think does most of the steps automatically. Now, don't get me wrong, one should still check out the docs, etc. It requires svn, forrest and gpg to be on the path. If anyone is so inclined, they could put available checks in. Would probably be useful to have other validation steps, too.
[jira] Commented: (SOLR-764) facet.limit=-1 with facet.sort=false does not work in distributed search
[ https://issues.apache.org/jira/browse/SOLR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629880#action_12629880 ] Lars Kotthoff commented on SOLR-764: Have you tried a version which incorporates SOLR-755? This should have been fixed in that issue. facet.limit=-1 with facet.sort=false does not work in distributed search Key: SOLR-764 URL: https://issues.apache.org/jira/browse/SOLR-764 Project: Solr Issue Type: New Feature Affects Versions: 1.3 Reporter: Wojtek Piaseczny Fix For: 1.4 If you specify facet.limit=-1 and facet.sort=false, no facet results are returned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-764) facet.limit=-1 with facet.sort=false does not work in distributed search
[ https://issues.apache.org/jira/browse/SOLR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629892#action_12629892 ] Wojtek Piaseczny commented on SOLR-764: --- I want to show dynamic ranges for numeric facets. My (and probably most??) implementation for building dynamic ranges requires the numbers to be sorted by facet name rather than by occurrences. facet.limit=-1 with facet.sort=false does not work in distributed search Key: SOLR-764 URL: https://issues.apache.org/jira/browse/SOLR-764 Project: Solr Issue Type: New Feature Affects Versions: 1.3 Reporter: Wojtek Piaseczny Fix For: 1.4 If you specify facet.limit=-1 and facet.sort=false, no facet results are returned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-764) Support facet.sort=false (index order) with distributed search
[ https://issues.apache.org/jira/browse/SOLR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-764: -- Description: Distributed search does not currently support sorting facets by index order (facet.sort=false). (was: If you specify facet.limit=-1 and facet.sort=false, no facet results are returned. ) Summary: Support facet.sort=false (index order) with distributed search (was: facet.limit=-1 with facet.sort=false does not work in distributed search) Support facet.sort=false (index order) with distributed search -- Key: SOLR-764 URL: https://issues.apache.org/jira/browse/SOLR-764 Project: Solr Issue Type: New Feature Affects Versions: 1.3 Reporter: Wojtek Piaseczny Fix For: 1.4 Distributed search does not currently support sorting facets by index order (facet.sort=false). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-765) ant example fails if example/work directory doesn't exist
ant example fails if example/work directory doesn't exist - Key: SOLR-765 URL: https://issues.apache.org/jira/browse/SOLR-765 Project: Solr Issue Type: Bug Affects Versions: 1.3 Reporter: Lars Kotthoff Priority: Minor Running ant example when there's no example/work directory causes the build to fail because the task tries to delete the (non-existent) directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-765) ant example fails if example/work directory doesn't exist
[ https://issues.apache.org/jira/browse/SOLR-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kotthoff updated SOLR-765: --- Attachment: SOLR-755.patch Patch adding 'failonerror=false' to the delete in the example ant task. ant example fails if example/work directory doesn't exist - Key: SOLR-765 URL: https://issues.apache.org/jira/browse/SOLR-765 Project: Solr Issue Type: Bug Affects Versions: 1.3 Reporter: Lars Kotthoff Priority: Minor Attachments: SOLR-755.patch Running ant example when there's no example/work directory causes the build to fail because the task tries to delete the (non-existent) directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-764) Support facet.sort=false (index order) with distributed search
[ https://issues.apache.org/jira/browse/SOLR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kotthoff updated SOLR-764: --- Attachment: SOLR-764.patch Patch implementing support for facet.sort=false with distributed search. Simplified the existing code by removing things that weren't used and added an additional method to sort facets by term number. Note that this implementation is flawed -- there are no distributed term numbers, therefore it's possible that several facet values have the same term number because they come from different shards. In that case the lexicographic order of the value will be used to break the tie. It is possible that facet values are returned in a different order for distributed and local setups. The patch also adds a unit test, commented out because of the issues described above. Support facet.sort=false (index order) with distributed search -- Key: SOLR-764 URL: https://issues.apache.org/jira/browse/SOLR-764 Project: Solr Issue Type: New Feature Affects Versions: 1.3 Reporter: Wojtek Piaseczny Fix For: 1.4 Attachments: SOLR-764.patch Distributed search does not currently support sorting facets by index order (facet.sort=false). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-765) ant example fails if example/work directory doesn't exist
[ https://issues.apache.org/jira/browse/SOLR-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kotthoff updated SOLR-765: --- Attachment: (was: SOLR-755.patch) ant example fails if example/work directory doesn't exist - Key: SOLR-765 URL: https://issues.apache.org/jira/browse/SOLR-765 Project: Solr Issue Type: Bug Affects Versions: 1.3 Reporter: Lars Kotthoff Priority: Minor Attachments: SOLR-765.patch Running ant example when there's no example/work directory causes the build to fail because the task tries to delete the (non-existent) directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-765) ant example fails if example/work directory doesn't exist
[ https://issues.apache.org/jira/browse/SOLR-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kotthoff updated SOLR-765: --- Attachment: SOLR-765.patch I promise to clean up my solr-patch-mess and not attach the wrong patch again. ant example fails if example/work directory doesn't exist - Key: SOLR-765 URL: https://issues.apache.org/jira/browse/SOLR-765 Project: Solr Issue Type: Bug Affects Versions: 1.3 Reporter: Lars Kotthoff Priority: Minor Attachments: SOLR-765.patch Running ant example when there's no example/work directory causes the build to fail because the task tries to delete the (non-existent) directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-764) Support facet.sort=false (index order) with distributed search
[ https://issues.apache.org/jira/browse/SOLR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629949#action_12629949 ] Wojtek Piaseczny commented on SOLR-764: --- I notice this patch consolidates the FacetInfo class' 'topFacets' 'listFacets' into a single collection. Do you know why these were ever separate? I had guessed it was because when 'listFacets' was being populated (only when facet.sort=false), it was being populated with data that was already ordered correctly per shard, and that combining the data (while maintaining sort order) from each shard could be optimized beyond calling Arrays.sort(). Shouldn't the getTermSorted method always use name instead of term number? Support facet.sort=false (index order) with distributed search -- Key: SOLR-764 URL: https://issues.apache.org/jira/browse/SOLR-764 Project: Solr Issue Type: New Feature Affects Versions: 1.3 Reporter: Wojtek Piaseczny Fix For: 1.4 Attachments: SOLR-764.patch Distributed search does not currently support sorting facets by index order (facet.sort=false). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-765) ant example fails if example/work directory doesn't exist
[ https://issues.apache.org/jira/browse/SOLR-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629958#action_12629958 ] Hoss Man commented on SOLR-765: --- why don't you have an example/work directory? it's actually committed to svn as an empty directory, and explicitly included as an empty directory in the releases. (i'm completely surprised that the example works at all if you've manually deleted the work directory) ant example fails if example/work directory doesn't exist - Key: SOLR-765 URL: https://issues.apache.org/jira/browse/SOLR-765 Project: Solr Issue Type: Bug Affects Versions: 1.3 Reporter: Lars Kotthoff Priority: Minor Attachments: SOLR-765.patch Running ant example when there's no example/work directory causes the build to fail because the task tries to delete the (non-existent) directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-216) Improvements to solr.py
[ https://issues.apache.org/jira/browse/SOLR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629976#action_12629976 ] Dariusz Suchojad commented on SOLR-216: --- Hi Mike, I've joined the solrpy (http://code.google.com/p/solrpy/) project where I'd like to incorporate the changes I had made and to work on adding more features to the Python client. I hope to get back to the discussion when, like you said, it becomes more stable and popular. Improvements to solr.py --- Key: SOLR-216 URL: https://issues.apache.org/jira/browse/SOLR-216 Project: Solr Issue Type: Improvement Components: clients - python Affects Versions: 1.2 Reporter: Jason Cater Assignee: Mike Klaas Priority: Trivial Attachments: solr-solrpy-r5.patch, solr.py, solr.py, solr.py, solr.py, test_all.py I've taken the original solr.py code and extended it to include higher-level functions. * Requires python 2.3+ * Supports SSL (https://) schema * Conforms (mostly) to PEP 8 -- the Python Style Guide * Provides a high-level results object with implicit data type conversion * Supports batching of update commands -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-216) Improvements to solr.py
[ https://issues.apache.org/jira/browse/SOLR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629981#action_12629981 ] Mike Klaas commented on SOLR-216: - That's great! Be sure to update http://wiki.apache.org/solr/SolPython as the project progresses. Improvements to solr.py --- Key: SOLR-216 URL: https://issues.apache.org/jira/browse/SOLR-216 Project: Solr Issue Type: Improvement Components: clients - python Affects Versions: 1.2 Reporter: Jason Cater Assignee: Mike Klaas Priority: Trivial Attachments: solr-solrpy-r5.patch, solr.py, solr.py, solr.py, solr.py, test_all.py I've taken the original solr.py code and extended it to include higher-level functions. * Requires python 2.3+ * Supports SSL (https://) schema * Conforms (mostly) to PEP 8 -- the Python Style Guide * Provides a high-level results object with implicit data type conversion * Supports batching of update commands -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-766) Remove python client from 1.3 distribution
Remove python client from 1.3 distribution -- Key: SOLR-766 URL: https://issues.apache.org/jira/browse/SOLR-766 Project: Solr Issue Type: Task Components: clients - python Affects Versions: 1.3 Reporter: Mike Klaas Assignee: Mike Klaas Priority: Blocker Fix For: 1.3 see solr-dev thread: http://mail-archives.apache.org/mod_mbox/lucene-solr-dev/200809.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-766) Remove python client from 1.3 distribution
[ https://issues.apache.org/jira/browse/SOLR-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12630004#action_12630004 ] Mike Klaas commented on SOLR-766: - JIRA seems to be not allowing me to upload a patch. Here is the text of the proposed README: Note: As of version 1.3, Solr no longer comes bundled with a Python client. The existing client was not sufficiently maintained or tested as development of Solr progressed, and committers felt that the code was not up to our usual high standards of release. The client bundled with previous versions of Solr will continue to be available indefinitely at: http://svn.apache.org/viewvc/lucene/solr/tags/release-1.2.0/client/python/ Please see http://wiki.apache.org/solr/SolPython for information on third-party Solr python clients. Remove python client from 1.3 distribution -- Key: SOLR-766 URL: https://issues.apache.org/jira/browse/SOLR-766 Project: Solr Issue Type: Task Components: clients - python Affects Versions: 1.3 Reporter: Mike Klaas Assignee: Mike Klaas Priority: Blocker Fix For: 1.3 see solr-dev thread: http://mail-archives.apache.org/mod_mbox/lucene-solr-dev/200809.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-766) Remove python client from 1.3 distribution
[ https://issues.apache.org/jira/browse/SOLR-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-766: Attachment: SOLR-766.patch Remove python client from 1.3 distribution -- Key: SOLR-766 URL: https://issues.apache.org/jira/browse/SOLR-766 Project: Solr Issue Type: Task Components: clients - python Affects Versions: 1.3 Reporter: Mike Klaas Assignee: Mike Klaas Priority: Blocker Fix For: 1.3 Attachments: SOLR-766.patch see solr-dev thread: http://mail-archives.apache.org/mod_mbox/lucene-solr-dev/200809.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-767) logged hits should be num matching docs, not num returned
logged hits should be num matching docs, not num returned --- Key: SOLR-767 URL: https://issues.apache.org/jira/browse/SOLR-767 Project: Solr Issue Type: Bug Affects Versions: 1.3 Reporter: Yonik Seeley Priority: Minor Fix For: 1.3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-768) Set last_index_time in full-import command
[ https://issues.apache.org/jira/browse/SOLR-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wojtek Piaseczny updated SOLR-768: -- Attachment: SOLR-768.patch Patch sets last index time before doing a full-import Set last_index_time in full-import command -- Key: SOLR-768 URL: https://issues.apache.org/jira/browse/SOLR-768 Project: Solr Issue Type: Improvement Components: contrib - DataImportHandler Affects Versions: 1.3 Reporter: Wojtek Piaseczny Fix For: 1.4 Attachments: SOLR-768.patch Variables are being resolved before executing the full-import command, but the last_index_time is not set (not read from file). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-768) Set last_index_time in full-import command
Set last_index_time in full-import command -- Key: SOLR-768 URL: https://issues.apache.org/jira/browse/SOLR-768 Project: Solr Issue Type: Improvement Components: contrib - DataImportHandler Affects Versions: 1.3 Reporter: Wojtek Piaseczny Fix For: 1.4 Attachments: SOLR-768.patch Variables are being resolved before executing the full-import command, but the last_index_time is not set (not read from file). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-651) A SearchComponent for fetching TF-IDF values
[ https://issues.apache.org/jira/browse/SOLR-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll updated SOLR-651: - Attachment: SOLR-651.patch Addresses Noble's thoughts. A SearchComponent for fetching TF-IDF values Key: SOLR-651 URL: https://issues.apache.org/jira/browse/SOLR-651 Project: Solr Issue Type: New Feature Affects Versions: 1.3 Reporter: Noble Paul Assignee: Grant Ingersoll Priority: Minor Fix For: 1.4 Attachments: SOLR-651.patch, SOLR-651.patch A SearchComponent that can return TF-IDF vector for any given document in the SOLR index Query : A Document Number / a query identifying a Document Response : A Map of term vs.TF-IDF value of every term in the Selected Document Why ? Most of the Machine Learning Algorithms work on TFIDF representation of documents, hence adding a Request Handler proving the TFIDF representation will pave the way for incorporating Learning Paradigms to SOLR framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-769) Support Document and Search Result clustering
Support Document and Search Result clustering - Key: SOLR-769 URL: https://issues.apache.org/jira/browse/SOLR-769 Project: Solr Issue Type: New Feature Reporter: Grant Ingersoll Assignee: Grant Ingersoll Priority: Minor Clustering is a useful tool for working with documents and search results, similar to the notion of dynamic faceting. Carrot2 (http://project.carrot2.org/) is a nice, BSD-licensed, library for doing search results clustering. Mahout (http://lucene.apache.org/mahout) is well suited for whole-corpus clustering. The patch I lays out a contrib module that starts off w/ an integration of a SearchComponent for doing clustering and an implementation using Carrot. In search results mode, it will use the DocList as the input for the cluster. While Carrot2 comes w/ a Solr input component, it is not the same as the SearchComponent that I have in that the Carrot example actually submits a query to Solr, whereas my SearchComponent is just chained into the Component list and uses the ResponseBuilder to add in the cluster results. While not fully fleshed out yet, the collection based mode will take in a list of ids or just use the whole collection and will produce clusters. Since this is a longer, typically offline task, there will need to be some type of storage mechanism (and replication??) for the clusters. I _may_ push this off to a separate JIRA issue, but I at least want to present the use case as part of the design of this component/contrib. It may even make sense that we split this out, such that the building piece is something like an UpdateProcessor and then the SearchComponent just acts as a lookup mechanism. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-768) Set last_index_time in full-import command
[ https://issues.apache.org/jira/browse/SOLR-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-768: Attachment: SOLR-768.patch makes sense. This value can be set irrespective of the the command. So it is moved to runCmd() Set last_index_time in full-import command -- Key: SOLR-768 URL: https://issues.apache.org/jira/browse/SOLR-768 Project: Solr Issue Type: Improvement Components: contrib - DataImportHandler Affects Versions: 1.3 Reporter: Wojtek Piaseczny Fix For: 1.4 Attachments: SOLR-768.patch, SOLR-768.patch Variables are being resolved before executing the full-import command, but the last_index_time is not set (not read from file). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
