[jira] Updated: (SOLR-256) Stats via JMX
[ https://issues.apache.org/jira/browse/SOLR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-256: -- Attachment: jmx.patch Sharad: my concern with your most recent patch is that if a servlet container uses it's own config to drive programmatic JMX Server creation (jetty plus appears to do this past on the example jetty-jmx.xml config file, but i haven't actually confirmed this), then Solr won't detect it because it's looking explicitly for the system properties. based on the javadocs your findMBeanServer(null) idea seems right on the money ... i'm attaching a tweak to your patch that uses this appraoch, and it seems to work great, what do you think? (was there a reason you decided to look for the properties explicitly instead of try this appraoch?) Any JMX experts want to chime in whether we should be doing something differently? Stats via JMX - Key: SOLR-256 URL: https://issues.apache.org/jira/browse/SOLR-256 Project: Solr Issue Type: New Feature Components: search, update Reporter: Sharad Agarwal Priority: Minor Attachments: jmx.patch, jmx.patch, jmx.patch, jmx.patch, jmx.patch This patch adds JMX capability to get statistics from all the SolrInfoMBean. The implementation is done such a way to minimize code changes. In SolrInfoRegistry, I have overloaded Map's put and remove methods to register and unregister SolrInfoMBean in MBeanServer. Later on, I am planning to use register and unregister methods in SolrInfoRegistry and removing getRegistry() method (Hiding the map instance to other classes) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-308) Add a field that generates an unique id when you have none in your data to index
[ https://issues.apache.org/jira/browse/SOLR-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514154 ] Thomas Peuss commented on SOLR-308: --- Hoss Man: I change the code in the way you described. Thanks for your notes on that. Add a field that generates an unique id when you have none in your data to index Key: SOLR-308 URL: https://issues.apache.org/jira/browse/SOLR-308 Project: Solr Issue Type: New Feature Components: search Reporter: Thomas Peuss Priority: Minor Attachments: GeneratedId.patch This patch adds a field that generates an unique id when you have no unique id in your data you want to index. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-313) Document-level metadata support
Document-level metadata support --- Key: SOLR-313 URL: https://issues.apache.org/jira/browse/SOLR-313 Project: Solr Issue Type: New Feature Components: search Reporter: Doğacan Güney Priority: Minor See discussion here: http://www.nabble.com/Passing-arguments-to-analyzers-t4096382.html The idea is to add metadata to documents (besides fields) and enable analyzers to access this metadata. A simple use case may be putting language information in document metadata and stemming document fields according to language. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-313) Document-level metadata support
[ https://issues.apache.org/jira/browse/SOLR-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doğacan Güney updated SOLR-313: --- Attachment: schema.xml stem-example.xml solr_document_meta.patch An kind-of-ugly hackish solution (suggested by Yonik Seeley [who also noted that it is hackish] on the mailing list) that adds a globally accessible thread local MetaParams class. This patch also adds a MultiLingualStemFilterFactory that reads language information from metadata and returns that language's SnowballFilter. To pass extra information during indexing, one can add it like this: doc field ... ... meta name=language content=German/ /doc And to pass extra information during search time, one can add it like this: http://localhost:8993/solr/select?q=meta.language=German Prefix meta. is used to avoid conflicts with other query parameters. Also attached is a sample document and schema for testing. Document-level metadata support --- Key: SOLR-313 URL: https://issues.apache.org/jira/browse/SOLR-313 Project: Solr Issue Type: New Feature Components: search Reporter: Doğacan Güney Priority: Minor Attachments: schema.xml, solr_document_meta.patch, stem-example.xml See discussion here: http://www.nabble.com/Passing-arguments-to-analyzers-t4096382.html The idea is to add metadata to documents (besides fields) and enable analyzers to access this metadata. A simple use case may be putting language information in document metadata and stemming document fields according to language. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-308) Add a field that generates an unique id when you have none in your data to index
[ https://issues.apache.org/jira/browse/SOLR-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Peuss updated SOLR-308: -- Attachment: UUIDField.patch Patch for an UUIDField and associated test. Add a field that generates an unique id when you have none in your data to index Key: SOLR-308 URL: https://issues.apache.org/jira/browse/SOLR-308 Project: Solr Issue Type: New Feature Components: search Reporter: Thomas Peuss Priority: Minor Attachments: GeneratedId.patch, UUIDField.patch This patch adds a field that generates an unique id when you have no unique id in your data you want to index. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-139) Support updateable/modifiable documents
[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514234 ] Yonik Seeley commented on SOLR-139: --- Thanks Mike, I've made those changes to my local copy. Support updateable/modifiable documents --- Key: SOLR-139 URL: https://issues.apache.org/jira/browse/SOLR-139 Project: Solr Issue Type: Improvement Components: update Reporter: Ryan McKinley Assignee: Ryan McKinley Attachments: getStoredFields.patch, getStoredFields.patch, getStoredFields.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-ModifyInputDocuments.patch, SOLR-139-ModifyInputDocuments.patch, SOLR-139-XmlUpdater.patch, SOLR-269+139-ModifiableDocumentUpdateProcessor.patch It would be nice to be able to update some fields on a document without having to insert the entire document. Given the way lucene is structured, (for now) one can only modify stored fields. While we are at it, we can support incrementing an existing value - I think this only makes sense for numbers. for background, see: http://www.nabble.com/loading-many-documents-by-ID-tf3145666.html#a8722293 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
