[jira] Commented: (SOLR-877) Access to Lucene's TermEnum capabilities

[ https://issues.apache.org/jira/browse/SOLR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653207#action_12653207 ] Noble Paul commented on SOLR-877: - No changes in the TermComponent API (I mean the HTTP API).

[jira] Commented: (SOLR-877) Access to Lucene's TermEnum capabilities

[ https://issues.apache.org/jira/browse/SOLR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653202#action_12653202 ] Yonik Seeley commented on SOLR-877: --- Regardless of how optimizations are selected or turned

[jira] Commented: (SOLR-877) Access to Lucene's TermEnum capabilities

[ https://issues.apache.org/jira/browse/SOLR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653201#action_12653201 ] Noble Paul commented on SOLR-877: - autosuggest is a very commonly used feature. And when they

[jira] Commented: (SOLR-877) Access to Lucene's TermEnum capabilities

[ https://issues.apache.org/jira/browse/SOLR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653189#action_12653189 ] Yonik Seeley commented on SOLR-877: --- Noble: would optionally using something like a radix t

[jira] Commented: (SOLR-877) Access to Lucene's TermEnum capabilities

[ https://issues.apache.org/jira/browse/SOLR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653187#action_12653187 ] Yonik Seeley commented on SOLR-877: --- lol - didn't take too long for other faceting like fea

[jira] Commented: (SOLR-877) Access to Lucene's TermEnum capabilities

[ https://issues.apache.org/jira/browse/SOLR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653184#action_12653184 ] Noble Paul commented on SOLR-877: - We may need a faster solution for the autoSuggest feature.

[jira] Commented: (SOLR-885) Generify NamedListCodec

[ https://issues.apache.org/jira/browse/SOLR-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653177#action_12653177 ] Noble Paul commented on SOLR-885: - OK. let us not make the change and stick to the original d

[jira] Commented: (SOLR-893) Unable to delete documents via SQL and deletedPkQuery with deltaimport

[ https://issues.apache.org/jira/browse/SOLR-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653176#action_12653176 ] Noble Paul commented on SOLR-893: - instead of adding the check in each method it can be added

[jira] Commented: (SOLR-284) Parsing Rich Document Types

[ https://issues.apache.org/jira/browse/SOLR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653137#action_12653137 ] Grant Ingersoll commented on SOLR-284: -- I think in multicore you can specify a shared li

[jira] Updated: (SOLR-893) Unable to delete documents via SQL and deletedPkQuery with deltaimport

[ https://issues.apache.org/jira/browse/SOLR-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Rosher updated SOLR-893: Attachment: SOLR-893.patch If there are no rows to fetch from the datasource, then null the rowIterator .. t

[jira] Created: (SOLR-893) Unable to delete documents via SQL and deletedPkQuery with deltaimport

Unable to delete documents via SQL and deletedPkQuery with deltaimport -- Key: SOLR-893 URL: https://issues.apache.org/jira/browse/SOLR-893 Project: Solr Issue Type: Bug

[jira] Commented: (SOLR-284) Parsing Rich Document Types

[ https://issues.apache.org/jira/browse/SOLR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652993#action_12652993 ] Chris Harris commented on SOLR-284: --- Currently this patch deploys the Tika libs to /trunk/e

[jira] Updated: (SOLR-284) Parsing Rich Document Types

[ https://issues.apache.org/jira/browse/SOLR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Harris updated SOLR-284: -- Attachment: SOLR-284.patch As I mentioned before, tests for these solr.client.solrj.embedded.JettyWeb

Re: Solr nightly build failure

[junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 17.101 sec [junit] Test org.apache.solr.client.solrj.embedded.SolrExampleJettyTest FAILED Any thoughts on this? Things are building fine on my local system and on hudson: http://hudson.zones.apache.org/hudson/job/Solr-trunk/

[jira] Commented: (SOLR-799) Add support for hash based exact/near duplicate document handling

[ https://issues.apache.org/jira/browse/SOLR-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652923#action_12652923 ] Ryan McKinley commented on SOLR-799: I'm not sure how you have the test set up, so I coul

[jira] Issue Comment Edited: (SOLR-799) Add support for hash based exact/near duplicate document handling

[ https://issues.apache.org/jira/browse/SOLR-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652837#action_12652837 ] [EMAIL PROTECTED] edited comment on SOLR-799 at 12/3/08 10:45 AM:

[jira] Updated: (SOLR-877) Access to Lucene's TermEnum capabilities

[ https://issues.apache.org/jira/browse/SOLR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Khee Chin updated SOLR-877: --- Attachment: SOLR-877.patch As req, however, I have only done a single test case, but it should be trivial to a

[jira] Commented: (SOLR-799) Add support for hash based exact/near duplicate document handling

[ https://issues.apache.org/jira/browse/SOLR-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652837#action_12652837 ] Mark Miller commented on SOLR-799: -- Okay, I see. I was too intent on changing the current ch

[jira] Commented: (SOLR-799) Add support for hash based exact/near duplicate document handling

[ https://issues.apache.org/jira/browse/SOLR-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652836#action_12652836 ] Yonik Seeley commented on SOLR-799: --- bq. Now that I look to fix this, I am not understandin

[jira] Commented: (SOLR-828) A RequestProcessor to support updates

[ https://issues.apache.org/jira/browse/SOLR-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652828#action_12652828 ] Noble Paul commented on SOLR-828: - A lot of useful comments on the mail thread http://markm

Re: Can we use Berkley DB java in Solr

On Wed, Dec 3, 2008 at 5:52 PM, Grant Ingersoll <[EMAIL PROTECTED]> wrote: > > On Dec 3, 2008, at 1:28 AM, Noble Paul നോബിള്‍ नोब्ळ् wrote: > >> The code can be written against JDBC. But we need to test the DDL and >> data types on al the supported DBs >> >> But , which one would we like to ship wi

[jira] Commented: (SOLR-799) Add support for hash based exact/near duplicate document handling

[ https://issues.apache.org/jira/browse/SOLR-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652815#action_12652815 ] Mark Miller commented on SOLR-799: -- I'm going to put up another patch for this soon. I'd lik

Re: Can we use Berkley DB java in Solr

Also, whatever is chosen needs to scale to millions of documents, and I wonder about an embedded DB doing that. I also have a hard time believing that both a DB w/ millions of docs and Solr can live on the same machine, which is presumably what an embedded DB must do. Presumably, it also ne

Re: Can we use Berkley DB java in Solr

On Dec 3, 2008, at 7:22 AM, Grant Ingersoll wrote: On Dec 3, 2008, at 1:28 AM, Noble Paul നോബിള്‍ नोब्ळ् wrote: The code can be written against JDBC. But we need to test the DDL and data types on al the supported DBs But , which one would we like to ship with Solr as a default option?

Re: Can we use Berkley DB java in Solr

On Dec 3, 2008, at 1:28 AM, Noble Paul നോബിള്‍ नोब्ळ् wrote: The code can be written against JDBC. But we need to test the DDL and data types on al the supported DBs But , which one would we like to ship with Solr as a default option? Why do we need a default option? Is this something th

Re: Can we use Berkley DB java in Solr

Noble Paul നോബിള്‍ नोब्ळ् wrote: The code can be written against JDBC. But we need to test the DDL and data types on al the supported DBs But , which one would we like to ship with Solr as a default option? H2 looks impressive. the jar (small) is just 667KB and the memory footprint is small to

Solr nightly build failure

init-forrest-entities: [mkdir] Created dir: /tmp/apache-solr-nightly/build [mkdir] Created dir: /tmp/apache-solr-nightly/build/web compile-common: [mkdir] Created dir: /tmp/apache-solr-nightly/build/common [javac] Compiling 40 source files to /tmp/apache-solr-nightly/build/common