[jira] Updated: (SOLR-139) Support updateable/modifiable documents

2007-02-04 Thread Ryan McKinley (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-139: --- Attachment: SOLR-139-IndexDocumentCommand.patch Support updateable/modifiable documents

Re: Connecting custom RequestHandler

2007-02-04 Thread Thorsten Scherler
On Sat, 2007-02-03 at 18:41 -0800, Ryan McKinley wrote: The 'new' request parser reads the content type header to see if it should parse the body as params or not. If the content type is application/x-www-form-urlencoded it parses them as params, if it is multipart/* it parses them as

[jira] Commented: (SOLR-139) Support updateable/modifiable documents

2007-02-04 Thread Yonik Seeley (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470061 ] Yonik Seeley commented on SOLR-139: --- Haven't had a chance to check out any code, but a few quick comments: If the

[jira] Updated: (SOLR-124) use NewIndexModifier, LUCENE-565

2007-02-04 Thread Yonik Seeley (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-124: -- Summary: use NewIndexModifier, LUCENE-565 (was: use LUCENE-565) LUCEUE-565 has been committed, but Solr

[jira] Commented: (SOLR-139) Support updateable/modifiable documents

2007-02-04 Thread Ryan McKinley (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470081 ] Ryan McKinley commented on SOLR-139: Is this what you are suggesting? I added a second searcher to

[jira] Commented: (SOLR-139) Support updateable/modifiable documents

2007-02-04 Thread Ryan McKinley (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470082 ] Ryan McKinley commented on SOLR-139: That wouldn't work for multi-valued fields though, right? 'REMOVE' on a

SOLR-1.1 Performance Tuning

2007-02-04 Thread Fuad Efendi
Hello, Can I send COMMIT and OPTIMIZE concurrently to ADD/DELETE? I temporary send it via synchronized method call. About 100 adds/deletes per second, commit each 1000 adds/deletes, and optimize each 1. Thanks, Fuad

Float Values shown as 1.2E7

2007-02-04 Thread Fuad Efendi
Hello, http://www.tokenizer.org shows price (in CAD$) 1.2E7 instead of 1199.99 (that is real!) I use sfloat for a price field... If you see different page, click 'refresh' F5; HTTP Caching... Thanks, Fuad

Re: SOLR-1.1 Performance Tuning

2007-02-04 Thread Yonik Seeley
On 2/4/07, Fuad Efendi [EMAIL PROTECTED] wrote: Hello, Can I send COMMIT and OPTIMIZE concurrently to ADD/DELETE? Yes, but adds will block while a commit or optimize is in progress. I temporary send it via synchronized method call. About 100 adds/deletes per second, commit each 1000

Re: Float Values shown as 1.2E7

2007-02-04 Thread Yonik Seeley
On 2/4/07, Fuad Efendi [EMAIL PROTECTED] wrote: Hello, http://www.tokenizer.org shows price (in CAD$) 1.2E7 instead of 1199.99 (that is real!) I use sfloat for a price field... An IEEE float only has 24 mantissa bits (7 decimal digits) of precision. 24*log(2)/log(10) = 7.22 Try an

RE: Float Values shown as 1.2E7

2007-02-04 Thread Fuad Efendi
Try an sdouble if you need exact prices that large. Thanks, Will it broke my indexes if I modify schema.xml and restart Tomcat?

Re: Float Values shown as 1.2E7

2007-02-04 Thread Yonik Seeley
On 2/4/07, Fuad Efendi [EMAIL PROTECTED] wrote: Try an sdouble if you need exact prices that large. Thanks, Will it broke my indexes if I modify schema.xml and restart Tomcat? Yes, float isn't compatible with double since they are essentially stored in a modified IEEE format. You will need

Re: finer granularity of configuration

2007-02-04 Thread Yonik Seeley
On 2/3/07, Erik Hatcher [EMAIL PROTECTED] wrote: I'd like to be able to have a common schema.xml and solrconfig.xml but be able to fire up Solr instances pointed to different data directories. I realize we have SOLR-79 in JIRA. Is that the approach we want long term? Here's an off-the-cuff

[jira] Commented: (SOLR-113) Some example + post.sh in docs in client/solrb

2007-02-04 Thread Antonio Eggberg (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470093 ] Antonio Eggberg commented on SOLR-113: -- Erik: Cool features you added this weekend. We can close this issue as

Re: AutoCommitTest failing

2007-02-04 Thread Yonik Seeley
On 2/4/07, Yonik Seeley [EMAIL PROTECTED] wrote: With the latest changes to AutoCommitTest, now I'm getting failures: [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 5.593 sec [junit] Test org.apache.solr.update.AutoCommitTest FAILED Stack trace: INFO: Opening [EMAIL

Re: AutoCommitTest failing

2007-02-04 Thread Yonik Seeley
On 2/4/07, Ryan McKinley [EMAIL PROTECTED] wrote: is this on your machine or on the apache machine? I have never had a problem running on my machine. My local machine happens every time now. I think Erik said it was failing for him also. -Yonik

Re: AutoCommitTest failing

2007-02-04 Thread Ryan McKinley
Can you tell specifically what part triggers the bad behavior? or is it whenever autocommit gets triggered? I wish I could be more useful, but from my system (win XP, jdk1.5.0_07) things look ok... On 2/4/07, Yonik Seeley [EMAIL PROTECTED] wrote: On 2/4/07, Ryan McKinley [EMAIL PROTECTED]

[jira] Commented: (SOLR-139) Support updateable/modifiable documents

2007-02-04 Thread Ryan McKinley (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470109 ] Ryan McKinley commented on SOLR-139: I added a new version of SOLR-139-IndexDocumentCommand.patch that: * gets rid

[jira] Commented: (SOLR-60) Remove overwritePending, overwriteCommitted flags?

2007-02-04 Thread Ryan McKinley (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470110 ] Ryan McKinley commented on SOLR-60: --- As a note, there are no tests where overwritePending != overwriteCommitted

Re: AutoCommitTest failing

2007-02-04 Thread Ryan McKinley
still trying (in vain) to make this fail on my setup... The one line that looks suspicious from your stack trace is: WARNING: best effort to remove C:\DOCUME~1\Yonik\LOCALS~1\Temp\org.apache.solr.update.AutoCommitTest-testMaxDocs-1170627577515 FAILED ! can you delete the directory

Re: AutoCommitTest failing

2007-02-04 Thread Erik Hatcher
On Feb 4, 2007, at 8:34 PM, Yonik Seeley wrote: On 2/4/07, Ryan McKinley [EMAIL PROTECTED] wrote: is this on your machine or on the apache machine? I have never had a problem running on my machine. My local machine happens every time now. I think Erik said it was failing for him also.

Re: AutoCommitTest failing

2007-02-04 Thread Yonik Seeley
On 2/4/07, Yonik Seeley [EMAIL PROTECTED] wrote: OK, the wildcard seems to be norton antivirus. Antivirus on: BUILD FAILED Total time: 2 minutes 22 seconds Antivirus off: BUILD SUCCESSFUL Total time: 1 minute 24 seconds Not yet sure why that would make the difference... and only on this test.

Re: AutoCommitTest failing

2007-02-04 Thread Ryan McKinley
hymmm. what do you think the best option is? Should we increase the time it waits to check if stuff autocommited? It currently waits 1 second for something that *should* start an autocommit within 1/2 sec. Is the RejectedExecutionException only thrown because JUnit failed? or is this an

[jira] Created: (SOLR-141) Errors/Exceptions should be formated by ResponseWriter

2007-02-04 Thread Hoss Man (JIRA)
Errors/Exceptions should be formated by ResponseWriter -- Key: SOLR-141 URL: https://issues.apache.org/jira/browse/SOLR-141 Project: Solr Issue Type: Wish Reporter: Hoss Man