gmane.comp.jakarta.lucene.devel

Re: Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java6-64 #175

Mark Miller — 2012-05-24T15:33:32

Finally got the same fail on my Windows virt machine - seems harder for me to see, but at least a confirmation.

- Mark Miller
lucidimagination.com

[jira] [Commented] (LUCENE-3523) WordBreakSpellChecker

James Dyer (JIRA — 2012-05-24T15:03:56

    [ https://issues.apache.org/jira/browse/LUCENE-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282551#comment-13282551 ] 

James Dyer commented on LUCENE-3523:
------------------------------------

This patch contains a standalone feature and doesn't affect anything else.  I would like to commit this sometime soon (and SOLR-2993 to integrate word-break spelling corrections in Solr).  This is a feature our previous search engine has that Lucene/Solr so far do not have.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

RE: Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java6-64 #175

Uwe Schindler — 2012-05-24T14:55:38

Hi,

The Jenkins Workspace is installed c:\Jenkins, so outside home dir. In that
case it should not be affected by Indexing. I can check this later.


It happens not all the time. Just as reminder: This VM has 2 virtual
CPUs/cores!

have

Lucene itsself has it.

weighed
my

[jira] [Comment Edited] (LUCENE-4006) system requirements is duplicated across versioned/unversioned

Uwe Schindler (JIRA — 2012-05-24T14:50:55

    [ https://issues.apache.org/jira/browse/LUCENE-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281904#comment-13281904 ] 

Uwe Schindler edited comment on LUCENE-4006 at 5/24/12 2:49 PM:
----------------------------------------------------------------

-Robert: The forrested one is now gone as we used a chainsaw, right? So I think we can close this issue :-)-
                
      was (Author: thetaphi):
    Robert: The forrested one is now gone as we used a chainsaw, right? So I think we can close this issue :-)
                  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (LUCENE-4006) system requirements is duplicated across versioned/unversioned

Uwe Schindler (JIRA — 2012-05-24T14:48:55

    [ https://issues.apache.org/jira/browse/LUCENE-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282538#comment-13282538 ] 

Uwe Schindler commented on LUCENE-4006:
---------------------------------------

LUCENE-1154 is the reason for the duplication:
- We had at that time no per-release docs with sysreqs. So at the time of 3.0, we had to support previous Lucene versions, too (which had no sysreq docs). So the general info is on the web page.

As we already removed the 2.x releases from the website, we no longer need the sysreqs global page and just refer to the per-version docs.

For Lucene 4.0 ewe have to add a markdown version to the release bundle.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (LUCENE-4006) system requirements is duplicated across versioned/unversioned

Uwe Schindler (JIRA — 2012-05-24T14:48:55

[ https://issues.apache.org/jira/browse/LUCENE-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282538#comment-13282538 ]

Uwe Schindler edited comment on LUCENE-4006 at 5/24/12 2:48 PM:
----------------------------------------------------------------

LUCENE-1154 is the reason for the duplication: We had at that time no per-release docs with sysreqs. So at the time of 3.0, we had to support previous Lucene versions, too (which had no sysreq docs). So the general info is on the web page.

As we already removed the 2.x releases from the website, we no longer need the sysreqs global page and just refer to the per-version docs.

For Lucene 4.0 ewe have to add a markdown version to the release bundle.

was (Author: thetaphi):
LUCENE-1154 is the reason for the duplication:
- We had at that time no per-release docs with sysreqs. So at the time of 3.0, we had to support previous Lucene versions, too (which had no sysreq docs). So the general info is on the web page.

As we already removed the 2.x releases from the website, we no longer need the sysreqs global page and just refer to the per-version docs.

For Lucene 4.0 ewe have to add a markdown version to the release bundle.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Yonik Seeley (JIRA — 2012-05-24T14:44:58

    [ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282532#comment-13282532 ] 

Yonik Seeley commented on SOLR-139:
-----------------------------------

bq. The schema has "price" and "price_c" (copy field from price)

For this feature to work correctly, source fields (the ones you normally send in) should be stored, and copyField targets (like price_c) should be un-stored.
                
 R-139.patch, SOLR-139.patch, SOLR-269+139-ModifiableDocumentUpdateProcessor.patch, getStoredFields.patch, getStoredFields.patch, getStoredFields.patch, getStoredFields.patch, getStoredFields
 .patch

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

Robert Muir (JIRA — 2012-05-24T14:18:56

    [ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282511#comment-13282511 ] 

Robert Muir commented on LUCENE-2878:
-------------------------------------

its fantastic how you guys have brought this back from the dead!
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java6-64 #175

Mark Miller — 2012-05-24T14:11:19

FWIW, I've been looping this test on my Windows 7 VM and I have not seen a single failure.

Perhaps we should have some Windows retry logic? Not the first time we have needed that I think.


On May 24, 2012, at 2:29 AM, Uwe Schindler wrote:


Are there excludes for the lucene/solr dirs? Been I while since I was weighed down with windows, but that always killed my indexing if I didn't exclude my checkout directories.

- Mark Miller
lucidimagination.com

Re: SOLR-2923

Mark Miller — 2012-05-24T14:05:53

I'll take it if no one beats me.

On May 24, 2012, at 9:15 AM, Adrien Grand wrote:


- Mark Miller
lucidimagination.com

[jira] [Commented] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

Alan Woodward (JIRA — 2012-05-24T13:56:12

    [ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282509#comment-13282509 ] 

Alan Woodward commented on LUCENE-2878:
---------------------------------------

I'll start on the offsets - some relatively mindless coding is probably about where I'm at today, and the brief look I had at ExactPhraseScorer scared me a bit.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

Simon Willnauer (JIRA — 2012-05-24T13:46:59

    [ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282507#comment-13282507 ] 

Simon Willnauer commented on LUCENE-2878:
-----------------------------------------

Alan this is awesome. I fixed some compile errors in solr and modules land and test-core passes! I will go ahead and commit this to the branch.
I think next is either fixing all missing queries (PhraseScorer and friends) or exposing offsets. Feel free to create a subtask for the offsets though. My first step here would be to put the offsets next to PositionInterval#begin/end as offsetBegin/End. This is more of a coding task than anything else in the beginning since this info needs to be transported up the PositionIntervalIterator "tree" during execution. on the lowest level (TermPositions) you can simply assign it via DocsAndPositionsEnum#start/endOffset() since that returns -1 if offsets are not indexed. 

thanks & good job!
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

Simon Willnauer (JIRA — 2012-05-24T13:42:26

    [ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282506#comment-13282506 ] 

Simon Willnauer commented on LUCENE-2878:
-----------------------------------------

Alan this is awesome. I fixed some compile errors in solr and modules land and test-core passes! I will go ahead and commit this to the branch.
I think next is either fixing all missing queries (PhraseScorer and friends) or exposing offsets. Feel free to create a subtask for the offsets though. My first step here would be to put the offsets next to PositionInterval#begin/end as offsetBegin/End. This is more of a coding task than anything else in the beginning since this info needs to be transported up the PositionIntervalIterator "tree" during execution. on the lowest level (TermPositions) you can simply assign it via DocsAndPositionsEnum#start/endOffset() since that returns -1 if offsets are not indexed. 

thanks & good job!
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SOLR-3485) Make /browse (files and handlers) dependencies self URL-contained

Raphaël Droz (JIRA — 2012-05-24T13:35:55

     [ https://issues.apache.org/jira/browse/SOLR-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raphaël Droz updated SOLR-3485:
-------------------------------

    Comment: was deleted

(was: Not really a blocker but whitelisting allowed files is probably the preferred way.)
    

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (SOLR-3485) Make /browse (files and handlers) dependencies self URL-contained

Raphaël Droz (JIRA — 2012-05-24T13:35:55

    [ https://issues.apache.org/jira/browse/SOLR-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282500#comment-13282500 ] 

Raphaël Droz edited comment on SOLR-3485 at 5/24/12 1:34 PM:
-------------------------------------------------------------

patch affects the example configuration :
* changes the location of expected for jquery.autocomplete.* and main.css
* creates the corresponding /browse/file solr.admin.ShowFileRequestHandler.

It makes use of the patch provided in issue SOLR-1833 in order to provide access to the restricted set of files absolutely needed and explicitly allowed.
                
      was (Author: drzraf):
    patch affects the example configuration :
* changes the location of expected for jquery.autocomplete.* and main.css
* creates the corresponding /browse/file solr.admin.ShowFileRequestHandler.

It makes use of the patch provided in issue #SOLR-1833 in order to provide access to the restricted set of files absolutely needed and explicitly allowed.
                  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SOLR-3485) Make /browse (files and handlers) dependencies self URL-contained

Raphaël Droz (JIRA — 2012-05-24T13:30:54

     [ https://issues.apache.org/jira/browse/SOLR-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raphaël Droz updated SOLR-3485:
-------------------------------

    Attachment: SOLR-3485-browse-static-files-URL-1.patch

patch affects the example configuration :
* changes the location of expected for jquery.autocomplete.* and main.css
* creates the corresponding /browse/file solr.admin.ShowFileRequestHandler.

It makes use of the patch provided in issue #SOLR-1833 in order to provide access to the restricted set of files absolutely needed and explicitly allowed.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (LUCENE-2878) Allow Scorer to expose positions and payloads aka. nuke spans

Alan Woodward (JIRA — 2012-05-24T13:24:57

     [ https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Woodward updated LUCENE-2878:
----------------------------------

    Attachment: LUCENE-2878.patch

Patch changing the Scorer#positions() signature to Scorer#positions(needsPayloads, needsOffsets), and implementing the payload passing functionality.  All Span payload tests now pass.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SOLR-3485) Make /browse (files and handlers) dependencies self URL-contained

Raphaël Droz (JIRA — 2012-05-24T13:21:55

Raphaël Droz created SOLR-3485:
----------------------------------

             Summary: Make /browse (files and handlers) dependencies self URL-contained
                 Key: SOLR-3485
                 URL: https://issues.apache.org/jira/browse/SOLR-3485
             Project: Solr
          Issue Type: Improvement
          Components: web gui
    Affects Versions: 4.0
            Reporter: Raphaël Droz
            Priority: Minor


Assuming that /browse may be, now or later, safe for a public use it would be very useful to make it "self-contained" in a given URL pattern in order to allow URL-based access restrictions.

There are 3 issues here :
* static files (css/js/img)
* external handlers like /terms, /clustering
* pattern switch between /browse/* and /collection1/browse/*

I only try to address the 1st issue, in the comment below.
If both /terms and /clustering are safe to be public, then issue 2 may be omitted.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

SOLR-2923

Adrien Grand — 2012-05-24T13:15:17

Hi,

Could someone review SOLR-2923 [1]? Although the patch is a little
old, the bug still exists in trunk and the patch applies correctly.

Thank you!

1. https://issues.apache.org/jira/browse/SOLR-2923

[jira] [Updated] (LUCENE-4062) More fine-grained control over the packed integer implementation that is chosen

Adrien Grand (JIRA — 2012-05-24T12:58:55

     [ https://issues.apache.org/jira/browse/LUCENE-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrien Grand updated LUCENE-4062:
---------------------------------

    Attachment: LUCENE-4062.patch

New patch. I added a VInt flag to the streams generated by writers so that the readers can know how to parse the stream. All tests passed.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SOLR-1833) ShowFileRequestHandle should allow you to specify which files can be viewed, not just which cannot be viewed

Raphaël Droz (JIRA — 2012-05-24T12:37:27

     [ https://issues.apache.org/jira/browse/SOLR-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raphaël Droz updated SOLR-1833:
-------------------------------

    Attachment: SOLR-1833-ShowFileRequestHandler-whitelist.patch

This patch may do the trick.
Still unsure about invariants.getParams() return value (could it be an empty Set ?).

Whitelisting takes precedence thus overrules any "hidden" invariant. I think this is a relatively safe behavior.

                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira