[jira] Commented: (LUCENE-2161) Some concurrency improvements for NRT

[ https://issues.apache.org/jira/browse/LUCENE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874454#action_12874454 ] Shay Banon commented on LUCENE-2161: Thanks! > Some concurrency improvements for NRT

[jira] Updated: (LUCENE-2484) Remove deprecated TermAttribute from tokenattributes and legacy support in indexer

[ https://issues.apache.org/jira/browse/LUCENE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2484: -- Attachment: LUCENE-2484.patch Updated patch, that also fixes a bug in NumericTokenStreams isAs

[jira] Commented: (LUCENE-2425) An Anti-Merging Multi-Directory Indexing Framework

[ https://issues.apache.org/jira/browse/LUCENE-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874445#action_12874445 ] Otis Gospodnetic commented on LUCENE-2425: -- Karthick, it looks like your May 1st

[jira] Updated: (SOLR-1852) enablePositionIncrements="true" can cause searches to fail when they are parsed as phrase queries

[ https://issues.apache.org/jira/browse/SOLR-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-1852: -- Attachment: SOLR-1852_solr14branch.patch here is the patch for solr 1.4. This also fixes SOLR-1706 > en

[jira] Updated: (SOLR-1852) enablePositionIncrements="true" can cause searches to fail when they are parsed as phrase queries

[ https://issues.apache.org/jira/browse/SOLR-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-1852: -- Fix Version/s: 1.4.1 > enablePositionIncrements="true" can cause searches to fail when they are > parse

[jira] Commented: (LUCENE-2348) DuplicateFilter incorrectly handles multiple calls to getDocIdSet for segment readers

[ https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874373#action_12874373 ] Trejkaz commented on LUCENE-2348: - I attempted to make a test but it fails with matching 0

[jira] Commented: (LUCENE-2348) DuplicateFilter incorrectly handles multiple calls to getDocIdSet for segment readers

[ https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874370#action_12874370 ] Trejkaz commented on LUCENE-2348: - What you describe is precisely the problem. It will de

Solr Security

I am running a Solr Application and I am authenticating the url using BASIC Tomcat. Essentially I want users to only be able to /select/* and admins to be able to do everything else. Right now I am checking for /select/* - Users /admin/* - Admin /update/* - Admin Are there other url strings I sh

Re: Push for a Solr 1.4.1 Bug Fix Release?

On Tue, Jun 1, 2010 at 7:57 PM, Chris Hostetter wrote: > > yeah ... totally understandable, like i said i just hadn't noticed it -- > you'll get no objection from me if you want to backport it. > ok i will look at merging this one later tonight / tomorrow unless someone pipes up. > : One altern

[jira] Resolved: (LUCENE-2300) IndexWriter should never pool readers for external segments

[ https://issues.apache.org/jira/browse/LUCENE-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2300. Fix Version/s: 3.0.2 3.1 Resolution: Fixed > IndexWriter

Re: Push for a Solr 1.4.1 Bug Fix Release?

: Yeah this was fixed for a while in trunk. I am only being a pain in the ass : about it because Peter (the reporter) has been patiently waiting for some : decision on what to do about it... I do think its sneaky, i mean stopword : before punctuation is probably pretty common :) yeah ... totally

Re: Push for a Solr 1.4.1 Bug Fix Release?

On Tue, Jun 1, 2010 at 7:39 PM, Chris Hostetter wrote: > > > SOLR-1852: i never even noticed this issue to consider it because i was > only looking at things marked "Resolved" in the 1.5, 3.1, or 4.0 branch (i > was only looking for things we already had fixes for) and this issue is > still marked

[jira] Updated: (LUCENE-2135) IndexReader.close should forcefully evict entries from FieldCache

[ https://issues.apache.org/jira/browse/LUCENE-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2135: --- Fix Version/s: 3.0.2 3.1 > IndexReader.close should forcefully ev

[jira] Assigned: (LUCENE-2356) Enable setting the terms index divisor used by IndexWriter whenever it opens internal readers

[ https://issues.apache.org/jira/browse/LUCENE-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reassigned LUCENE-2356: -- Assignee: Michael McCandless > Enable setting the terms index divisor used by

Re: Push for a Solr 1.4.1 Bug Fix Release?

: LUCENE-2466: didn't show up in my lists because it's a LUCENE issue ... ...if you do merge that one, we should probably have a new SOLR issue for tracking the commits to the "pre-merged-trunk" branch-1.4 ... we can mark it as a child of, or dependent on LUCENE-2466. -Hoss --

Re: Push for a Solr 1.4.1 Bug Fix Release?

: > All of the planned issues for 1.4.1 have been committed to branch-1.4, and : > : : just wondering, where was this planning? Earlier in the thread -- i posted a list of 18 issues that i was planning on merging, and got feedback saying "good idea", but besides upgrading to 2.9.2 (or 2.9.3) n

[jira] Resolved: (LUCENE-2161) Some concurrency improvements for NRT

[ https://issues.apache.org/jira/browse/LUCENE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2161. Resolution: Fixed > Some concurrency improvements for NRT > --

RE: svn commit: r950300 - /lucene/java/branches/lucene_2_9/src/java/org/apache/lucene/store/NativeFSLockFactory.java

Oh no, good catch! :-) Better than too late! - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: mikemcc...@apache.org [mailto:mikemcc...@apache.org] > Sent: Wednesday, June 02, 2010 1:07 AM > To: java-comm.

Re: Push for a Solr 1.4.1 Bug Fix Release?

On Tue, Jun 1, 2010 at 6:19 PM, Chris Hostetter wrote: > > All of the planned issues for 1.4.1 have been committed to branch-1.4, and > just wondering, where was this planning? > but it would be great if > folks interested in helping out with testing could check out branch-1.4 > and take it for

[jira] Commented: (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=12874290#action_12874290 ] Steven Rowe commented on LUCENE-2167: - bq. This version uses Character.toUpperCase() [

Re: Push for a Solr 1.4.1 Bug Fix Release?

All of the planned issues for 1.4.1 have been committed to branch-1.4, and i've upgraded it to Lucene 2.9.2. We will most likely be waiting for Lucene 2.9.3 to be ready (at least as a release candidate) before publishing any Solr 1.4.1 release candidates, but it would be great if folks intere

[jira] Commented: (SOLR-1934) branch-1.4 should use Lucene 2.9.3

[ https://issues.apache.org/jira/browse/SOLR-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874272#action_12874272 ] Hoss Man commented on SOLR-1934: Committed revision 950282. ...I updated branch-1.4 to use

[jira] Commented: (SOLR-1934) branch-1.4 should use Lucene 2.9.3

[ https://issues.apache.org/jira/browse/SOLR-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874264#action_12874264 ] Uwe Schindler commented on SOLR-1934: - I will do my best! > branch-1.4 should use Lucen

Re: Distributed Search Components

Hi, All, IIUC, the core requirement here is to be able to search across multiple (mirror) copies of a certain index. If so, you may want to consider taking a look at the Mirroring Split Policy, which in turn is based on An Anti-Merging Multi-Direc

[jira] Updated: (SOLR-1934) branch-1.4 should use Lucene 2.9.3

[ https://issues.apache.org/jira/browse/SOLR-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-1934: --- Summary: branch-1.4 should use Lucene 2.9.3 (was: branch-1.4 should use Lucene 2.9.2) clear push for Lucene

[jira] Updated: (LUCENE-2161) Some concurrency improvements for NRT

[ https://issues.apache.org/jira/browse/LUCENE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2161: --- Fix Version/s: 3.0.2 3.1 > Some concurrency improvements for NRT

[jira] Commented: (LUCENE-2161) Some concurrency improvements for NRT

[ https://issues.apache.org/jira/browse/LUCENE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874253#action_12874253 ] Michael McCandless commented on LUCENE-2161: Shay it will be backported to 3.0

[jira] Commented: (LUCENE-2311) Pass potent SR to IRWarmer.warm(), and also call warm() for new segments

[ https://issues.apache.org/jira/browse/LUCENE-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874249#action_12874249 ] Michael McCandless commented on LUCENE-2311: bq. From the user's standpoint wa

Re: Distributed Search Components

: has anyone considered the ParallelMultiSearcher for distributed search? : Perhaps it is not neccessary to implement code that takes care of the : distributed part of a search, if we make a Solr-server thinking, that he : searches only one index. AS i understand it, part of the reason this type

[jira] Updated: (LUCENE-2356) Enable setting the terms index divisor used by IndexWriter whenever it opens internal readers

[ https://issues.apache.org/jira/browse/LUCENE-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2356: --- Attachment: LUCENE-2356.patch Simple patch -- adds IWC.set/getReaderTermsIndexDiviso

Re: Lucene 2.9.3 ? ( blocking Solr 1.4.1 ? ? ? )

: > but the majority don't have any patch at all. : : Hmm only 3 right? You can see them as the OPEN ones (not REOPENED), sorry .. correct, not sure why i wrote "majority" ... clearly false. If all the OPEN issues marked against 2.9.3 either alreayd have patches, or have people working on tri

Re: Lucene 2.9.3 ? ( blocking Solr 1.4.1 ? ? ? )

+1 for end-of-day Thu freeze -- I'll finish mine by then. But I think for trivial fixes for kinda bad bugs (LUCENE-2311 -- real bad: mergedSegmentWarner is basically unusable; LUCENE-2356) we should make an exception (allow them into 2.9.3)? I've already got the patch up for 2311; I'll do 2356 sh

[jira] Commented: (LUCENE-2311) Pass potent SR to IRWarmer.warm(), and also call warm() for new segments

[ https://issues.apache.org/jira/browse/LUCENE-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874224#action_12874224 ] Earwin Burrfoot commented on LUCENE-2311: - This is not the issue of reader turnaro

RE: Lucene 2.9.3 ? ( blocking Solr 1.4.1 ? ? ? )

Hi all, I am quite fine with doing a 2.9.3 / 3.0.2 release as soon as possible, but I don't like to force any reopened issues into this release. I have no problem with doing this in parallel to the Solr 1.4.1 Release. I don't think that it is a good idea, to now reopen a lot of issues, just to get

[jira] Updated: (LUCENE-2311) Pass potent SR to IRWarmer.warm(), and also call warm() for new segments

[ https://issues.apache.org/jira/browse/LUCENE-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2311: --- Attachment: LUCENE-2311.patch New patch, includes trivial fix (test passes) and CHAN

Re: Distributing pylucene on Linux

Sanjeet Kumar wrote: > Hi, > > We are using pylucence in an application and have compiled and build jcc > and pylucene successfully on Debian/Ubuntu. > > We now want to be able to "distribute" our application as a more or less > self-contained zip file for use on any flavor of Linux (eg. CentO

[jira] Commented: (LUCENE-2311) Pass potent SR to IRWarmer.warm(), and also call warm() for new segments

[ https://issues.apache.org/jira/browse/LUCENE-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874214#action_12874214 ] Michael McCandless commented on LUCENE-2311: bq. It is also arguably more conc

[jira] Updated: (LUCENE-2311) Pass potent SR to IRWarmer.warm(), and also call warm() for new segments

[ https://issues.apache.org/jira/browse/LUCENE-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2311: --- Attachment: LUCENE-2311.patch Test case showing the issue. Basically you cannot run

[jira] Resolved: (SOLR-1933) improve solr indenting

[ https://issues.apache.org/jira/browse/SOLR-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley resolved SOLR-1933. Resolution: Fixed > improve solr indenting > -- > > Key: SOLR-19

[jira] Commented: (LUCENE-2348) DuplicateFilter incorrectly handles multiple calls to getDocIdSet for segment readers

[ https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874185#action_12874185 ] Michael McCandless commented on LUCENE-2348: I don't understand the problem he

[jira] Updated: (LUCENE-2348) DuplicateFilter incorrectly handles multiple calls to getDocIdSet for segment readers

[ https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2348: --- Fix Version/s: (was: 4.0) (was: 3.0.2)

Re: Lucene 2.9.3 ? ( blocking Solr 1.4.1 ? ? ? )

On Tue, Jun 1, 2010 at 2:48 PM, Chris Hostetter wrote: > > : I'd really like to get most of those back-ported, for 2.9.3. I'm > : actively working on this today. I was the one who went and marked > : them as 2.9.3 in the first place on Sat :). > > Ok ... i mainly just wanted ot make sure we were

[jira] Commented: (SOLR-1405) Show the index files in the web UI

[ https://issues.apache.org/jira/browse/SOLR-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874173#action_12874173 ] Andrzej Bialecki commented on SOLR-1405: - .. in particular ParallelReader.directory

[jira] Commented: (SOLR-1405) Show the index files in the web UI

[ https://issues.apache.org/jira/browse/SOLR-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874168#action_12874168 ] Hoss Man commented on SOLR-1405: There's a general concensus that we should stop adding new

[jira] Resolved: (LUCENE-2421) Hardening of NativeFSLock

[ https://issues.apache.org/jira/browse/LUCENE-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2421. Resolution: Fixed > Hardening of NativeFSLock > - > >

[jira] Updated: (LUCENE-2466) fix some more locale problems in lucene/solr

[ https://issues.apache.org/jira/browse/LUCENE-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2466: Fix Version/s: 3.1 4.0 setting fix versions correctly here. happy to backport

Re: Lucene 2.9.3 ? ( blocking Solr 1.4.1 ? ? ? )

: I'd really like to get most of those back-ported, for 2.9.3. I'm : actively working on this today. I was the one who went and marked : them as 2.9.3 in the first place on Sat :). Ok ... i mainly just wanted ot make sure we were all on the same page about what issues were being targed for 2.9

[jira] Resolved: (LUCENE-2104) IndexWriter.unlock does does nothing if NativeFSLockFactory is used

[ https://issues.apache.org/jira/browse/LUCENE-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2104. Resolution: Fixed > IndexWriter.unlock does does nothing if NativeFSLockFactory is

[jira] Updated: (LUCENE-2394) Factories for cache creation

[ https://issues.apache.org/jira/browse/LUCENE-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2394: --- Fix Version/s: 4.0 (was: 3.0.2) (was: 2

Re: Lucene 2.9.3 ? ( blocking Solr 1.4.1 ? ? ? )

I'd really like to get most of those back-ported, for 2.9.3. I'm actively working on this today. I was the one who went and marked them as 2.9.3 in the first place on Sat :). But, 2394 I don't think should block 2.9.3. I'll go push it out... Mike On Tue, Jun 1, 2010 at 2:12 PM, Chris Hostette

Lucene 2.9.3 ? ( blocking Solr 1.4.1 ? ? ? )

My suggestion that we do a Solr 1.4.1 bug fix seems to have gottne Uwe and McCandless all excited about doing a Lucene 2.9.3 release... https://issues.apache.org/jira/browse/SOLR-1934 ...but it's not clear to me how realisitc this is, or how close we are to seeing it happen. Beyond hte few

[jira] Commented: (SOLR-1933) improve solr indenting

[ https://issues.apache.org/jira/browse/SOLR-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874128#action_12874128 ] Hoss Man commented on SOLR-1933: bq. Didn't seem useful beyond that (an indent of 40 chars)

[jira] Commented: (SOLR-1933) improve solr indenting

[ https://issues.apache.org/jira/browse/SOLR-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874124#action_12874124 ] Yonik Seeley commented on SOLR-1933: bq. why stop at 20? Didn't seem useful beyond that

[jira] Resolved: (LUCENE-2046) IndexReader.isCurrent incorrectly returns false after writer.prepareCommit has been called

[ https://issues.apache.org/jira/browse/LUCENE-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2046. Resolution: Fixed > IndexReader.isCurrent incorrectly returns false after writer.p

[jira] Updated: (SOLR-1936) Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028)

[ https://issues.apache.org/jira/browse/SOLR-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-1936: --- Affects Version/s: 1.1.0 (was: 1.4) > Json output Incorrect escaping Unicod

[jira] Resolved: (LUCENE-2060) CMS should default its maxThreadCount to 1 (not 3)

[ https://issues.apache.org/jira/browse/LUCENE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2060. Resolution: Fixed > CMS should default its maxThreadCount to 1 (not 3) > -

[jira] Resolved: (SOLR-1936) Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028)

[ https://issues.apache.org/jira/browse/SOLR-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley resolved SOLR-1936. Fix Version/s: 1.4.1 (was: 1.4) Resolution: Fixed > Json output Incorr

[jira] Resolved: (LUCENE-2119) If you pass Integer.MAX_VALUE as 2nd param to search(Query, int) you hit unexpected NegativeArraySizeException

[ https://issues.apache.org/jira/browse/LUCENE-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2119. Fix Version/s: 3.0.2 3.1 Resolution: Fixed > If you pass

[jira] Commented: (SOLR-1316) Create autosuggest component

[ https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874084#action_12874084 ] Andrzej Bialecki commented on SOLR-1316: - I would expect the facet.prefix method to

[jira] Commented: (SOLR-1936) Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028)

[ https://issues.apache.org/jira/browse/SOLR-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874081#action_12874081 ] Yonik Seeley commented on SOLR-1936: Committed to trunk. I'll backport to 3.1 and 1.4.1

[jira] Commented: (SOLR-1936) Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028)

[ https://issues.apache.org/jira/browse/SOLR-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874072#action_12874072 ] Robert Hofstra commented on SOLR-1936: -- Tested SOLR-1936.patch and its working :) > J

[jira] Updated: (SOLR-1936) Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028)

[ https://issues.apache.org/jira/browse/SOLR-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-1936: --- Attachment: SOLR-1936.patch Here's my version of the patch. Perhaps your issue as caused by writing ou

[jira] Resolved: (LUCENE-2142) FieldCache.getStringIndex should not throw exception if term count exceeds doc count

[ https://issues.apache.org/jira/browse/LUCENE-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2142. Fix Version/s: 3.0.2 3.1 Resolution: Fixed > FieldCache.

[jira] Commented: (SOLR-1864) Master/Slave replication causes tomcat to be unresponsive on slave till replication is being done.

[ https://issues.apache.org/jira/browse/SOLR-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874055#action_12874055 ] Peter Karich commented on SOLR-1864: This might be a duplicate of: https://issues.apache

RE: Adding CLucene as a Lucene subproject

Grant, Thanks for your reply, and for the PMC on their time. I understand your reasoning. We hoped becoming a Lucene sub-project will bring us more attention. Being a TLP may miss that goal, although being an ASF TLP definitely has benefits of its own. We will discuss this internally and resume

RE: Adding CLucene as a Lucene subproject

Grant, Thanks for your reply, and for the PMC on their time. I understand your reasoning. We hoped becoming a Lucene sub-project will bring us more attention. Being a TLP may miss that goal, although being an ASF TLP definitely has benefits of its own. We will discuss this internally and resume

RE: Adding CLucene as a Lucene subproject

Grant, Thanks for your reply, and for the PMC on their time. I understand your reasoning. We hoped becoming a Lucene sub-project will bring us more attention. Being a TLP may miss that goal, although being an ASF TLP definitely has benefits of its own. We will discuss this internally and resume

[jira] Commented: (SOLR-1936) Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028)

[ https://issues.apache.org/jira/browse/SOLR-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874050#action_12874050 ] Robert Hofstra commented on SOLR-1936: -- When mapping to \u2028 ... case '\u2028': wri

[jira] Resolved: (LUCENE-2299) if you open an NRT reader while addIndexes* is running it may miss segments

[ https://issues.apache.org/jira/browse/LUCENE-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2299. Resolution: Fixed > if you open an NRT reader while addIndexes* is running it may

[jira] Resolved: (LUCENE-2424) FieldDoc.toString only returns super.toString

[ https://issues.apache.org/jira/browse/LUCENE-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2424. Resolution: Fixed > FieldDoc.toString only returns super.toString > --

Re: Adding CLucene as a Lucene subproject

Hi Itamar, Sorry for the delay, the holiday weekend snuck up on me sooner than I thought it would. The consensus on CLucene is that it should go through incubation with the idea of becoming a TLP on its own, if it wishes to be a part of the ASF. The primary reason for this is the ASF tries t

[jira] Commented: (SOLR-1936) Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028)

[ https://issues.apache.org/jira/browse/SOLR-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874027#action_12874027 ] Robert Hofstra commented on SOLR-1936: -- You're right, I try it, should I provide a new

[jira] Commented: (SOLR-1316) Create autosuggest component

[ https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874026#action_12874026 ] David Smiley commented on SOLR-1316: (re-post) For auto-complete, I use Solr's faceting

[jira] Commented: (LUCENE-2484) Remove deprecated TermAttribute from tokenattributes and legacy support in indexer

[ https://issues.apache.org/jira/browse/LUCENE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874024#action_12874024 ] Stanislaw Osinski commented on LUCENE-2484: --- {quote} Since this clustering contr

[jira] Commented: (SOLR-1936) Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028)

[ https://issues.apache.org/jira/browse/SOLR-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874021#action_12874021 ] Yonik Seeley commented on SOLR-1936: In the interest of not destroying information, we s

[jira] Updated: (SOLR-1936) Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028)

[ https://issues.apache.org/jira/browse/SOLR-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Hofstra updated SOLR-1936: - Description: The Unicode Character 'LINE SEPARATOR' (U+2028) is not escaped in json response, res

[jira] Commented: (LUCENE-2484) Remove deprecated TermAttribute from tokenattributes and legacy support in indexer

[ https://issues.apache.org/jira/browse/LUCENE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874017#action_12874017 ] Uwe Schindler commented on LUCENE-2484: --- Additionally: I will commit this soon. I do

[jira] Updated: (SOLR-1936) Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028)

[ https://issues.apache.org/jira/browse/SOLR-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Hofstra updated SOLR-1936: - Attachment: patch-SOLR-1936-TRUNK.patch patch for current trunk version ( 01-06-2010) > Json outp

[jira] Commented: (LUCENE-2484) Remove deprecated TermAttribute from tokenattributes and legacy support in indexer

[ https://issues.apache.org/jira/browse/LUCENE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874015#action_12874015 ] Robert Muir commented on LUCENE-2484: - Since this clustering contrib depends on binary

[jira] Updated: (SOLR-1936) Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028)

[ https://issues.apache.org/jira/browse/SOLR-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Hofstra updated SOLR-1936: - Attachment: patch-SOLR-1936.txt patch-SOLR-1936-test.txt patch for JSONResponseWri

[jira] Commented: (LUCENE-2484) Remove deprecated TermAttribute from tokenattributes and legacy support in indexer

[ https://issues.apache.org/jira/browse/LUCENE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874012#action_12874012 ] Uwe Schindler commented on LUCENE-2484: --- bq. Against which version of Lucene should

Re: Query Timings increase after system is idle

Thanks for the response, Mike. In our solution, the entire index is memory mapped. On Thu, May 20, 2010 at 2:05 PM, Mike Klaas wrote: > Solr and Lucene rely on the OS disk cache for speedy queries. If they > are left idle for hours while the disk is used for other purposes, the > OS will page

[jira] Commented: (LUCENE-2484) Remove deprecated TermAttribute from tokenattributes and legacy support in indexer

[ https://issues.apache.org/jira/browse/LUCENE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874008#action_12874008 ] Stanislaw Osinski commented on LUCENE-2484: --- Hi! Against which version of Lucen

[jira] Created: (SOLR-1936) Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028)

Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028) -- Key: SOLR-1936 URL: https://issues.apache.org/jira/browse/SOLR-1936 Project: Solr Issue Typ

[jira] Commented: (LUCENE-2484) Remove deprecated TermAttribute from tokenattributes and legacy support in indexer

[ https://issues.apache.org/jira/browse/LUCENE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874004#action_12874004 ] Robert Muir commented on LUCENE-2484: - bq. We cannot move forward in breaking backward

[jira] Commented: (LUCENE-2484) Remove deprecated TermAttribute from tokenattributes and legacy support in indexer

[ https://issues.apache.org/jira/browse/LUCENE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874002#action_12874002 ] Uwe Schindler commented on LUCENE-2484: --- So after hours of waiting: - Lucene Core, C

[jira] Updated: (LUCENE-2484) Remove deprecated TermAttribute from tokenattributes and legacy support in indexer

[ https://issues.apache.org/jira/browse/LUCENE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2484: -- Attachment: LUCENE-2484.patch > Remove deprecated TermAttribute from tokenattributes and legac

[jira] Updated: (LUCENE-2484) Remove deprecated TermAttribute from tokenattributes and legacy support in indexer

[ https://issues.apache.org/jira/browse/LUCENE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2484: -- Description: The title says it: - Remove interface TermAttribute - Remove empty fake implement

[jira] Created: (LUCENE-2484) Remove deprecated TermAttribute from tokenattributes and legacy support in indexer

Remove deprecated TermAttribute from tokenattributes and legacy support in indexer -- Key: LUCENE-2484 URL: https://issues.apache.org/jira/browse/LUCENE-2484 Project: Luc

[jira] Resolved: (LUCENE-2417) Fix IndexCommit hashCode() and equals() to be consistent

[ https://issues.apache.org/jira/browse/LUCENE-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2417. Resolution: Fixed > Fix IndexCommit hashCode() and equals() to be consistent > ---

[jira] Resolved: (LUCENE-2372) Replace deprecated TermAttribute by new CharTermAttribute

[ https://issues.apache.org/jira/browse/LUCENE-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir resolved LUCENE-2372. - Assignee: Uwe Schindler Resolution: Fixed everything is cutover to the new attribute now

[jira] Commented: (LUCENE-2372) Replace deprecated TermAttribute by new CharTermAttribute

[ https://issues.apache.org/jira/browse/LUCENE-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873964#action_12873964 ] Robert Muir commented on LUCENE-2372: - Committed LUCENE-2372_contrib_solr.patch revisi

[jira] Updated: (LUCENE-2372) Replace deprecated TermAttribute by new CharTermAttribute

[ https://issues.apache.org/jira/browse/LUCENE-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2372: Fix Version/s: 3.1 > Replace deprecated TermAttribute by new CharTermAttribute > -

Re: SolrCloud integration roadmap

Depending on free time and feedback, I hope to get it into trunk this week. -- - Mark http://www.lucidimagination.com On 6/1/10 6:55 AM, olivier sallou wrote: When should Cloud feature be merged in Lucene/Solr Merged trunk ? I saw that Cloud feature is expected in next Solr version If I need

Re: SolrCloud integration roadmap

When should Cloud feature be merged in Lucene/Solr Merged trunk ? I saw that Cloud feature is expected in next Solr version If I need to go to a pre-release version, I would rather like going to latest branch. 2010/6/1 Mark Miller > But keep in mind that that is based on a fairly older version

Re: SolrCloud integration roadmap

But keep in mind that that is based on a fairly older version of Solr now (pre Lucene/Solr merge). On 6/1/10 3:25 AM, Simon Willnauer wrote: Oliver, you can already get a snapshot from the branch https://svn.apache.org/repos/asf/lucene/solr/branches/cloud/ and see the wiki for details: http:/

Distributing pylucene on Linux

Hi, We are using pylucence in an application and have compiled and build jcc and pylucene successfully on Debian/Ubuntu. We now want to be able to "distribute" our application as a more or less self-contained zip file for use on any flavor of Linux (eg. CentOS, Redhat, etc.). It will contain our

[jira] Resolved: (LUCENE-2397) SnapshotDeletionPolicy.snapshot() throws NPE if no commits happened

[ https://issues.apache.org/jira/browse/LUCENE-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2397. Resolution: Fixed > SnapshotDeletionPolicy.snapshot() throws NPE if no commits hap

[jira] Commented: (LUCENE-2299) if you open an NRT reader while addIndexes* is running it may miss segments

[ https://issues.apache.org/jira/browse/LUCENE-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873923#action_12873923 ] Michael McCandless commented on LUCENE-2299: bq. So is in 3.1. Yes. > if you

[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 ] Uwe Schindler updated LUCENE-2167: -- Attachment: LUCENE-2167-jflex-tld-macro-gen.patch Updated patch. I had not seen that the prev

  1   2   >