Re: Build failed in Hudson: Lucene-trunk #1181

This test failure is caused by a known bug in Java: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6588260 We are working around it (avoiding this Java API) in the pending fix on https://issues.apache.org/jira/browse/LUCENE-2449... Mike On Fri, May 7, 2010 at 10:17 PM, Apache Hudson Server

Re: Adding another dimension to Lucene searches

On 2010-05-07 18:25, mark harwood wrote: > I have been working on a hierarchical search capability for a while now and > wanted to see if there was general interest in adopting some of the thinking > into Lucene. > > The idea needs a little explanation so I've put some slides up here to kick >

Build failed in Hudson: Solr-trunk #1144

See Changes: [hossman] SOLR-1843: new rootName attribute for configuration ... allows users to override the top level name for MBeans when exposed via JMX. [rmuir] SOLR-1865: ignore BOMs in SolrResourceLoader.getLines [rmuir]

Re: Adding another dimension to Lucene searches

OK, seems like there is some interest. I'll work on packaging the code/unit tests/demos and make it available. > matching ids ... but I didn't quite catch from the slides how you encode > the parent-child link... is it just "the next docs are sub-documents > until the next parent doc"? Yes - us

[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr

[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865441#action_12865441 ] Erik Hatcher commented on SOLR-1163: For drilling into facets using fq, the queries real

[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr

[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865445#action_12865445 ] Uri Boness commented on SOLR-1163: -- @Lance there was always a timeout in solr explorer whic

[jira] Updated: (LUCENE-2167) Implement StandardTokenizer with the UAX#29 Standard

[ https://issues.apache.org/jira/browse/LUCENE-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Rowe updated LUCENE-2167: Attachment: LUCENE-2167.patch I added your change removing CharBuffer.wrap(), Robert, and it appea

Re: Adding another dimension to Lucene searches

On 5/8/10 3:10 AM, Mark Harwood wrote: The downside is the need to maintain sequences of related docs in the same segment - something Lucene currently doesn't make easy with its limited control over when segments are flushed. I suspect we'll need some discussion on how best to support this.

[jira] Commented: (LUCENE-1585) Allow to control how payloads are merged

[ https://issues.apache.org/jira/browse/LUCENE-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865487#action_12865487 ] Shai Erera commented on LUCENE-1585: I've been thinking about the multi-threading issu

[jira] Commented: (SOLR-1013) Scan code for equality implementation mistakes

[ https://issues.apache.org/jira/browse/SOLR-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865508#action_12865508 ] Lance Norskog commented on SOLR-1013: - Please close this. On further study of this parti

[jira] Closed: (SOLR-1013) Scan code for equality implementation mistakes

[ https://issues.apache.org/jira/browse/SOLR-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley closed SOLR-1013. -- Resolution: Invalid > Scan code for equality implementation mistakes > -

[jira] Created: (SOLR-1907) Solr Embedded server has no URI addressing scheme

Solr Embedded server has no URI addressing scheme - Key: SOLR-1907 URL: https://issues.apache.org/jira/browse/SOLR-1907 Project: Solr Issue Type: Improvement Components: clients - jav

[jira] Commented: (SOLR-1907) Solr Embedded server has no URI addressing scheme

[ https://issues.apache.org/jira/browse/SOLR-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865510#action_12865510 ] Lance Norskog commented on SOLR-1907: - This patch would have 3 parts: # Establish *solr

[jira] Updated: (SOLR-1907) Solr Embedded server has no URI addressing scheme

[ https://issues.apache.org/jira/browse/SOLR-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lance Norskog updated SOLR-1907: Description: There is a URI scheme for addressing Solr via HTTP, but there is no URI scheme availab

[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr

[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865513#action_12865513 ] Lance Norskog commented on SOLR-1163: - .bq In the new version this will be configured pe

Re: Adding another dimension to Lucene searches

There are two separate problems that I know of in indexing parts of PDFs in an overlapping way: 1) block-structured documents of a) the entire PDF file b) chapters c) sections of chapters d.z) 2) Tracking the set of pages that each document contains. As I understand this, LUCENE

[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr

[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865521#action_12865521 ] Uri Boness commented on SOLR-1163: -- @Lance Oh... right... indeed that's a bug :(. Since I

Hudson build is back to normal : Lucene-3.x #7

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Build failed in Hudson: Lucene-trunk #1182

See Changes: [mikemccand] fix some eclipse warnings (thanks Shai!) [markrmiller] fix package oddities -- [...truncated 16093 lines...] [javadoc] Generating Javadoc [javadoc] Javadoc

[jira] Updated: (SOLR-1602) Refactor SOLR package structure to include o.a.solr.response and move QueryResponseWriters in there

[ https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated SOLR-1602: Attachment: SOLR-1602.Mattmann.final.050810.patch.txt > Refactor SOLR package structure to i

[jira] Commented: (SOLR-1602) Refactor SOLR package structure to include o.a.solr.response and move QueryResponseWriters in there

[ https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865532#action_12865532 ] Chris A. Mattmann commented on SOLR-1602: - Hey Hoss: I went ahead and got some time

[jira] Issue Comment Edited: (LUCENE-2167) Implement StandardTokenizer with the UAX#29 Standard

[ https://issues.apache.org/jira/browse/LUCENE-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865481#action_12865481 ] Steven Rowe edited comment on LUCENE-2167 at 5/9/10 1:05 AM: -

[jira] Updated: (LUCENE-2167) Implement StandardTokenizer with the UAX#29 Standard

[ https://issues.apache.org/jira/browse/LUCENE-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Rowe updated LUCENE-2167: Attachment: LUCENE-2167.patch Attached a patch that removes lookahead/chaining. All tests pass.

[jira] Commented: (SOLR-1568) Implement Spatial Filter

[ https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865543#action_12865543 ] Kyle Wilkinson commented on SOLR-1568: -- I was able to get this up and running with the

Re: Incremental Field Updates

Shai, I think this is an interesting approach. I can see how I could [incrementally] update a stored, indexed field this way, but I don't understand how I could update an indexed-only field. Here's why: for a stored (and indexed) field, I can always determine what terms to remove ('-') from the po

Re: Incremental Field Updates

No, actually, you can update index-only fields also. It all depends on the operation that you ask to do on the fields. For example, if the query to execute is something like "update all documents w/ tags:ibm -> remove terms t1, t2, t3 and add terms t4, t5", then the result of such request would dis