Re: Custom Directory and IndexInput

Thanks, that's exactly the response I was looking for. On Tue, Aug 21, 2012 at 9:31 AM, Uwe Schindler wrote: > Hi, > > ** ** > > It is required that every thread uses its own IndexInput. This is why e.g. > every search calls IndexInput.clone() several times while executing a > search query.

Re: [JENKINS] Lucene-Solr-Tests-trunk-java7 - Build # 3090 - Failure

> [junit4:junit4] ERROR: JVM J0 ended with an exception, command line: > /usr/local/openjdk7/jre/bin/java -XX:+UseG1GC - This happened the second time, java 1.7, G1GC but I couldn't reproduce it on jenkins machine (ran a full suite with the same seed a few times). If this happens again and someb

RE: Custom Directory and IndexInput

Hi, It is required that every thread uses its own IndexInput. This is why e.g. every search calls IndexInput.clone() several times while executing a search query. Because of that there are explicietly no thread safety requirements in IndexInput, but clone() must be implemented as a cheap met

[jira] [Updated] (LUCENE-4315) Minor fixes for Fields abstract class, TermVectorsWriter

[ https://issues.apache.org/jira/browse/LUCENE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-4315: -- Description: The Fields abstract class is a little bit inconsistent. It does not allow iterat

[jira] [Comment Edited] (LUCENE-4315) Minor fixes for Fields abstract class, TermVectorsWriter

[ https://issues.apache.org/jira/browse/LUCENE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438479#comment-13438479 ] Uwe Schindler edited comment on LUCENE-4315 at 8/21/12 5:24 PM: ---

[jira] [Commented] (LUCENE-4315) Minor fixes for Fields abstract class, TermVectorsWriter

[ https://issues.apache.org/jira/browse/LUCENE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438479#comment-13438479 ] Uwe Schindler commented on LUCENE-4315: --- Hi Mike, I already proposed that and opene

Custom Directory and IndexInput

I'm trying to build a custom directory implementation, actually the directory itself just fallback to one of the existing directory implementations, so it's actually more about IndexInput/IndexOutput. I have some concerns about my implementation, especially related to multithreading: - IndexOu

[jira] [Commented] (LUCENE-4316) Deprecate Fields.getUniqueTermCount, remove AtomicReader.getUniqueTermCount

[ https://issues.apache.org/jira/browse/LUCENE-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438478#comment-13438478 ] Uwe Schindler commented on LUCENE-4316: --- +1 > Deprecate Fields.get

[jira] [Comment Edited] (SOLR-3721) Multiple concurrent recoveries of same shard?

[ https://issues.apache.org/jira/browse/SOLR-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432948#comment-13432948 ] Per Steffensen edited comment on SOLR-3721 at 8/21/12 5:05 PM: --

[jira] [Commented] (LUCENE-4311) HunspellStemFilter returns another values than Hunspell in console / command line with same dictionaries.

[ https://issues.apache.org/jira/browse/LUCENE-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438471#comment-13438471 ] Chris Male commented on LUCENE-4311: I was able to replicate this behaviour and to ge

[jira] [Updated] (SOLR-3746) updateLog should fail to init if there is no _version_ field in schema.xml

[ https://issues.apache.org/jira/browse/SOLR-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-3746: --- Attachment: SOLR-3746.patch patch updating the VersionInfo class to throw an exception if the version field d

[jira] [Updated] (SOLR-3746) updateLog should fail to init if there is no _version_ field in schema.xml

[ https://issues.apache.org/jira/browse/SOLR-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-3746: --- Description: Per irc conversation with yonik, it's not clear if updateLog works correctly in all situations i

[jira] [Updated] (SOLR-3747) Solr Score threshold 'reasonably', independent of results returned

[ https://issues.apache.org/jira/browse/SOLR-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramzi Alqrainy updated SOLR-3747: - Description: Usually, search results are sorted by their score (how well the document matched the

[jira] [Updated] (SOLR-3747) Solr Score threshold 'reasonably', independent of results returned

[ https://issues.apache.org/jira/browse/SOLR-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramzi Alqrainy updated SOLR-3747: - Attachment: Screen Shot 2012-08-21 at 5.30.38 AM.png Pseudo Code > Solr Score thr

[jira] [Updated] (SOLR-3747) Solr Score threshold 'reasonably', independent of results returned

[ https://issues.apache.org/jira/browse/SOLR-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramzi Alqrainy updated SOLR-3747: - Attachment: (was: screenshot-1.jpg) > Solr Score threshold 'reasonably', independent of re

[jira] [Updated] (SOLR-3747) Solr Score threshold 'reasonably', independent of results returned

[ https://issues.apache.org/jira/browse/SOLR-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramzi Alqrainy updated SOLR-3747: - Attachment: screenshot-1.jpg > Solr Score threshold 'reasonably', independent of results retur

[jira] [Updated] (SOLR-3747) Solr Score threshold 'reasonably', independent of results returned

[ https://issues.apache.org/jira/browse/SOLR-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramzi Alqrainy updated SOLR-3747: - Summary: Solr Score threshold 'reasonably', independent of results returned (was: Solr Score thre

[jira] [Updated] (SOLR-3747) Solr Score threshold 'reasonably', independent of results returned?

[ https://issues.apache.org/jira/browse/SOLR-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramzi Alqrainy updated SOLR-3747: - Description: Usually, search results are sorted by their score (how well the document matched the

[jira] [Created] (SOLR-3747) Solr Score threshold 'reasonably', independent of results returned?

Ramzi Alqrainy created SOLR-3747: Summary: Solr Score threshold 'reasonably', independent of results returned? Key: SOLR-3747 URL: https://issues.apache.org/jira/browse/SOLR-3747 Project: Solr

[JENKINS] Lucene-Solr-Tests-trunk-java7 - Build # 3090 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-java7/3090/ All tests passed Build Log: [...truncated 7840 lines...] [junit4:junit4] ERROR: JVM J0 ended with an exception, command line: /usr/local/openjdk7/jre/bin/java -XX:+UseG1GC -Dtests.prefix=tests -Dtests.seed=53A82554C93E2753

[jira] [Resolved] (LUCENE-4314) The specification of DocIdSetIterator is needlessly ambiguous.

[ https://issues.apache.org/jira/browse/LUCENE-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-4314. Resolution: Fixed Fix Version/s: 4.0 5.0 Thanks Franco!

[jira] [Commented] (LUCENE-4314) The specification of DocIdSetIterator is needlessly ambiguous.

[ https://issues.apache.org/jira/browse/LUCENE-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438328#comment-13438328 ] Michael McCandless commented on LUCENE-4314: Thanks Franco, patch looks good!

[jira] [Commented] (LUCENE-4318) facets module has many tokenstreams that never call clearAttributes

[ https://issues.apache.org/jira/browse/LUCENE-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438302#comment-13438302 ] Robert Muir commented on LUCENE-4318: - Not only that, they actually depend upon this

[jira] [Created] (LUCENE-4318) facets module has many tokenstreams that never call clearAttributes

Robert Muir created LUCENE-4318: --- Summary: facets module has many tokenstreams that never call clearAttributes Key: LUCENE-4318 URL: https://issues.apache.org/jira/browse/LUCENE-4318 Project: Lucene - C

[jira] [Updated] (LUCENE-3849) position increments should be implemented by TokenStream.end()

[ https://issues.apache.org/jira/browse/LUCENE-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-3849: Attachment: LUCENE-3849.patch here is an updated patch, fixing all the analyzers and also removing

Re: Reviving DistributedSearch

Zack, I'm really pleased to see this you expressing interest in this. Some points that I'd like to make regarding the topic: - Distributed Search isn't just hard, it's really hard. - Lucene, and thus, Lucene.Net is a library, and anything which is contributed to it should remain within that scop

[jira] [Created] (SOLR-3746) updateLog should fail to init if there is no _version_ field in schema.xml

Hoss Man created SOLR-3746: -- Summary: updateLog should fail to init if there is no _version_ field in schema.xml Key: SOLR-3746 URL: https://issues.apache.org/jira/browse/SOLR-3746 Project: Solr Is

[jira] [Created] (SOLR-3745) SolrCore should fail to init in SolrCloud mode if schema does not contain _version_ field

Hoss Man created SOLR-3745: -- Summary: SolrCore should fail to init in SolrCloud mode if schema does not contain _version_ field Key: SOLR-3745 URL: https://issues.apache.org/jira/browse/SOLR-3745 Project: So

[jira] [Commented] (LUCENE-3849) position increments should be implemented by TokenStream.end()

[ https://issues.apache.org/jira/browse/LUCENE-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438244#comment-13438244 ] Robert Muir commented on LUCENE-3849: - {quote} where does the "positionIncrementGap"

[jira] [Created] (LUCENE-4317) Field.java does not reuse its inlined Keyword-TokenStream

Uwe Schindler created LUCENE-4317: - Summary: Field.java does not reuse its inlined Keyword-TokenStream Key: LUCENE-4317 URL: https://issues.apache.org/jira/browse/LUCENE-4317 Project: Lucene - Core

[jira] [Commented] (LUCENE-3849) position increments should be implemented by TokenStream.end()

[ https://issues.apache.org/jira/browse/LUCENE-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438237#comment-13438237 ] Hoss Man commented on LUCENE-3849: -- bq. should we do something like clearAttributes() +

[jira] [Commented] (LUCENE-3849) position increments should be implemented by TokenStream.end()

[ https://issues.apache.org/jira/browse/LUCENE-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438234#comment-13438234 ] Robert Muir commented on LUCENE-3849: - {quote} In addition we should also check all T

[jira] [Commented] (LUCENE-3849) position increments should be implemented by TokenStream.end()

[ https://issues.apache.org/jira/browse/LUCENE-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438232#comment-13438232 ] Robert Muir commented on LUCENE-3849: - What about the "off-by-one" though? Because th

[jira] [Commented] (LUCENE-3849) position increments should be implemented by TokenStream.end()

[ https://issues.apache.org/jira/browse/LUCENE-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438227#comment-13438227 ] Uwe Schindler commented on LUCENE-3849: --- +1 to call a full clearAttributes(). After

[jira] [Updated] (LUCENE-3849) position increments should be implemented by TokenStream.end()

[ https://issues.apache.org/jira/browse/LUCENE-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-3849: Attachment: LUCENE-3849.patch Here's a patch. There are some things I don't like about it though.

[jira] [Comment Edited] (SOLR-3741) ExtendedDismaxQParser (edismax) does not obey q.op for queries with operators

[ https://issues.apache.org/jira/browse/SOLR-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438208#comment-13438208 ] Lance Norskog edited comment on SOLR-3741 at 8/21/12 8:16 AM: --

[jira] [Commented] (LUCENE-4315) Minor fixes for Fields abstract class, TermVectorsWriter

[ https://issues.apache.org/jira/browse/LUCENE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438213#comment-13438213 ] Michael McCandless commented on LUCENE-4315: +1 Though ... I wonder if we sh

[jira] [Commented] (SOLR-3741) ExtendedDismaxQParser (edismax) does not obey q.op for queries with operators

[ https://issues.apache.org/jira/browse/SOLR-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438208#comment-13438208 ] Lance Norskog commented on SOLR-3741: - Please post a unit test matrix demonstrating the

Re: Diversifying Search Results - Custom Collector

If you do the same search twice in a row, the second search takes < 3 ms. Try finding your base result set and then augmenting it with a second search within the first result set. You can sort from a function call. Sorting is multi-level, so you can make one of the levels random. Does this app ha

[jira] [Commented] (LUCENE-4316) Deprecate Fields.getUniqueTermCount, remove AtomicReader.getUniqueTermCount

[ https://issues.apache.org/jira/browse/LUCENE-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438206#comment-13438206 ] Michael McCandless commented on LUCENE-4316: +1 > Deprecate

Re: Diversifying Search Results - Custom Collector

Hi Mikhail, You are correct. "[+] show 6 result.." will work but it wouldn't suit my requirements. This is a question of user experience right? Imagine if the product manager comes to you and says I dont want to see "[+] show 6 result.." and I want the results to be diverse bu

Grammar for ComplexPhraseQueryParser

Hello, Does anyone have the grammar file (.jj file) for the complex phrase query parser. The patch from https://issues.apache.org/jira/browse/SOLR-1604 does not have the grammar file as part of it. Thanks, Phani. -- View this message in context: http://lucene.472066.n3.nabble.com/Grammar-f

[jira] [Commented] (SOLR-1604) Wildcards, ORs etc inside Phrase Queries

[ https://issues.apache.org/jira/browse/SOLR-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438180#comment-13438180 ] Phani Vempaty commented on SOLR-1604: - Hello all, Could I get the grammar file (.jj f

[jira] [Commented] (SOLR-3684) Frequently full gc while do pressure index

[ https://issues.apache.org/jira/browse/SOLR-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438178#comment-13438178 ] Lance Norskog commented on SOLR-3684: - For multi-hosted Solr shops, per-collection thro

[jira] [Updated] (LUCENE-4316) Deprecate Fields.getUniqueTermCount, remove AtomicReader.getUniqueTermCount

[ https://issues.apache.org/jira/browse/LUCENE-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-4316: Attachment: LUCENE-4316.patch patch for branch_4x. I would remove the deprecation in trunk and fix

[jira] [Created] (LUCENE-4316) Deprecate Fields.getUniqueTermCount, remove AtomicReader.getUniqueTermCount

Robert Muir created LUCENE-4316: --- Summary: Deprecate Fields.getUniqueTermCount, remove AtomicReader.getUniqueTermCount Key: LUCENE-4316 URL: https://issues.apache.org/jira/browse/LUCENE-4316 Project: Lu

RE: large messages from Jenkins failures

+1 to using -Dtests.showOutput=never for Jenkins jobs. - Steve -Original Message- From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Behalf Of Dawid Weiss Sent: Monday, August 20, 2012 2:20 PM To: dev@lucene.apache.org Subject: Re: large messages from Jenkins failures This is

Re: Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true

: Because people impl the default algorithm for general purposes. Those : tailorings are not 'mandatory'. I didn't say they were mandatory, I said it seems like it would be a good idea to add options for them. The spec says: "... implementations may override (tailor) the results to meet the re

Re: Diversifying Search Results - Custom Collector

Hello, I don't believe your task can be solved by playing with scoring/collector or shuffling. For me it's absolutely Grouping usecase (despite I don't really know this feature well). > Grouping cannot solve the problem because I dont want to limit the number of results showed based on the groupi

[jira] [Assigned] (LUCENE-4314) The specification of DocIdSetIterator is needlessly ambiguous.

[ https://issues.apache.org/jira/browse/LUCENE-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reassigned LUCENE-4314: -- Assignee: Michael McCandless > The specification of DocIdSetIterator is ne

[jira] [Updated] (LUCENE-4314) The specification of DocIdSetIterator is needlessly ambiguous.

[ https://issues.apache.org/jira/browse/LUCENE-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franco Callari updated LUCENE-4314: --- Attachment: DocIdSetIterator.patch Patch for DocIdSetIterator's advance() javadoc

[jira] [Commented] (LUCENE-4315) Minor fixes for Fields abstract class, TermVectorsWriter

[ https://issues.apache.org/jira/browse/LUCENE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438078#comment-13438078 ] Robert Muir commented on LUCENE-4315: - {quote} size() is defined to return -1 if stat

[jira] [Commented] (LUCENE-4315) Minor fixes for Fields abstract class, TermVectorsWriter

[ https://issues.apache.org/jira/browse/LUCENE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438077#comment-13438077 ] Robert Muir commented on LUCENE-4315: - {quote} Can you open issue? I also agree that

[jira] [Comment Edited] (SOLR-3284) StreamingUpdateSolrServer swallows exceptions

[ https://issues.apache.org/jira/browse/SOLR-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438072#comment-13438072 ] Mikhail Khludnev edited comment on SOLR-3284 at 8/21/12 5:37 AM:

[jira] [Commented] (SOLR-3284) StreamingUpdateSolrServer swallows exceptions

[ https://issues.apache.org/jira/browse/SOLR-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438072#comment-13438072 ] Mikhail Khludnev commented on SOLR-3284: Hi, Excuse me for hijacking, but server-s

[jira] [Commented] (LUCENE-4314) The specification of DocIdSetIterator is needlessly ambiguous.

[ https://issues.apache.org/jira/browse/LUCENE-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438070#comment-13438070 ] Uwe Schindler commented on LUCENE-4314: --- Please use the upload functionality of thi

[jira] [Comment Edited] (LUCENE-4314) The specification of DocIdSetIterator is needlessly ambiguous.

[ https://issues.apache.org/jira/browse/LUCENE-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438060#comment-13438060 ] Franco Callari edited comment on LUCENE-4314 at 8/21/12 5:31 AM: --

[jira] [Commented] (LUCENE-4314) The specification of DocIdSetIterator is needlessly ambiguous.

[ https://issues.apache.org/jira/browse/LUCENE-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438060#comment-13438060 ] Franco Callari commented on LUCENE-4314: There we go... --- lucene-4.0.0-BETA/c

Re: large messages from Jenkins failures

Oh, one more thing -- if we suppress the console output we would absolutely have to keep (at jenkins) multiple tests-report.txt files because these always contain full output dumps (regardless of console settings). Otherwise we'd suppress potentially important info. Dawid On Mon, Aug 20, 2012 at

Re: large messages from Jenkins failures

This is partially aggregated by solr failure logs (the output for successful suites is not emitted to the console). As for myself I don't look at those e-mails directly, I typicall click on the jenkins link to see the full output. Alternatively we could suppress the console output for failures too

[jira] [Updated] (LUCENE-4315) Minor fixes for Fields abstract class, TermVectorsWriter

[ https://issues.apache.org/jira/browse/LUCENE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-4315: -- Attachment: LUCENE-4315.patch Updated patch: - size() is defined to return -1 if stat not avai

[jira] [Commented] (LUCENE-4315) Minor fixes for Fields abstract class, TermVectorsWriter

[ https://issues.apache.org/jira/browse/LUCENE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438041#comment-13438041 ] Uwe Schindler commented on LUCENE-4315: --- bq. But there is no need to have this on A

[jira] [Commented] (SOLR-3619) Rename 'example' dir to 'server' and pull examples into an 'examples' directory

[ https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438032#comment-13438032 ] Hoss Man commented on SOLR-3619: I started reading through this, and then got bogged down,

Re: Compilation issues

I already had IntelliJ configured, but it appears I needed to do ant idea again now, ant resolve wasn't enough Thanks for your help with this On Mon, Aug 20, 2012 at 8:28 PM, Steven A Rowe wrote: > Hi Itamar, > > ** ** > > I use Oracle JDK v1.7.0_01 64-bit with IntelliJ v11.1.3 on Windows

RE: Compilation issues

Hi Itamar, I use Oracle JDK v1.7.0_01 64-bit with IntelliJ v11.1.3 on Windows 7, and it works fine for me - I just did a full rebuild (Build|Rebuild Project) from a fresh trunk checkout, and compilation of all of Lucene/Solr succeeded with no errors. Have you seen

RE: Compilation issues

If you are using IntelliJ IDEA, then do "ant idea" from top-level. It should convert the whole checkout to a properly configured project. I am using Eclipse, where this works good: "ant eclipse"), for IDEA have a look at the output of "ant idea" for more instructions. - Uwe Schindler H.-H

RE: Compilation issues

Did you do "ant resolve" from top-level? It should place all needed jars in the lib folders. - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de From: itamar.synhers...@gmail.com [mailto:itamar.synhers...@gma

Re: Compilation issues

Makes sense, thanks Done that, and now it complains about carrotsearch.randomizedtesting not being found Also some other stuff like SystemPropertiesRestoreRule, TestMethodProvider, ThreadFilter, LifecycleScope etc Any idea what could be broken? On Mon, Aug 20, 2012 at 7:40 PM, Uwe Schindler wr

Re: twitter questions

I sent off the TL;DR portion of your answer with a permalink to the actual response on the archive. Thanks Christopher. On Mon, Aug 20, 2012 at 12:22 PM, Christopher Currens wrote: > In regards to the NIOFSDirectory, we have no plans on supporting it > for several reasons, the largest being that

[jira] [Commented] (LUCENE-4314) The specification of DocIdSetIterator is needlessly ambiguous.

[ https://issues.apache.org/jira/browse/LUCENE-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438003#comment-13438003 ] Michael McCandless commented on LUCENE-4314: Hi Franco, just attach the patch

RE: Compilation issues

ForbiddenApisCheckTask is only compiled using IVY from the command line for use inside build.xml. As those are only build tools, they are *not* nedded for the main Lucene and not needed to compile Lucene itsself. The resulting classes are never packaged anywhere, they are just for assisting build.x

Re: Reviving DistributedSearch

Nick, Thanks for the feedback. You may not have been looking for this long and complex of a reply, but I wanted to share my thinking and validate some assumptions with the group before I get too much further down the road. Let me walk you through where my thinking is at, and see what you think.

Why does this exception happen? Lucene exception

Our application is crashing every 2 hours or so and we are seeing a spike in database connections right before it. have not isolated the issue yet. Can someone respond what the exception below really mean and can it spike DB connection issues. Thank you. org.compass.core.engine.SearchEngineExcep

large messages from Jenkins failures

Is there any way we can limit the size of the messages Jenkins emails this list? Responsing to a "your mailbox is full" warning, I found I had 32 recent Jenkins messages all over 1mb (a few were >10mb). A few weeks ago I returned from vacation to find my mail account partially disabled because

Re: Diversifying Search Results - Custom Collector

Tanguy, You idea is perfect for cases where there is a too many documents with 80-90% documents having same value for a particular field. As an example, your idea is ideal for, lets say we have 10 documents in total like this, doc1 : Kellog's doc2 : Kellog's doc3 : Kellog's

[jira] [Commented] (LUCENENET-502) Recreate the missing files needed to build Lucene.Net.Distributed

[ https://issues.apache.org/jira/browse/LUCENENET-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437984#comment-13437984 ] Christopher Currens commented on LUCENENET-502: --- I would put it in trunk

Re: twitter questions

In regards to the NIOFSDirectory, we have no plans on supporting it for several reasons, the largest being that NIO (meaning New I/O) is a java only API. I guess it would be good to briefly discuss what NIO is in Java (anyone feel free to correct me when I inevitably get some of the details wrong

[jira] [Commented] (LUCENE-4314) The specification of DocIdSetIterator is needlessly ambiguous.

[ https://issues.apache.org/jira/browse/LUCENE-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437975#comment-13437975 ] Franco Callari commented on LUCENE-4314: Michael McCandless scripsit: > True ...

Re: Compilation issues

Thanks for your prompt response I'm using IntelliJ IDEA 11 on a Windows machine. ant clean + resolve didn't really make any difference. My c:\Program Files (x86)\Java\jre7\lib\ folder was missing tools.jar and ant was complaining about it so I grabbed it from one of IntelliJ's folders, but that d

[jira] [Updated] (LUCENENET-502) Recreate the missing files needed to build Lucene.Net.Distributed

[ https://issues.apache.org/jira/browse/LUCENENET-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zachary Gramana updated LUCENENET-502: -- Description: Zack Gramana - Recommend commit to trunk, and re-evaluate for 3.6 relea

[jira] [Commented] (LUCENE-4314) The specification of DocIdSetIterator is needlessly ambiguous.

[ https://issues.apache.org/jira/browse/LUCENE-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437968#comment-13437968 ] Michael McCandless commented on LUCENE-4314: bq. The current status is not th

[jira] [Updated] (LUCENENET-502) Recreate the missing files needed to build Lucene.Net.Distributed

[ https://issues.apache.org/jira/browse/LUCENENET-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prescott Nasser updated LUCENENET-502: -- Description: Zach Gramana - Recommend commit to trunk, and re-evaluate for 3.6

Re: Diversifying Search Results - Custom Collector

Hello, I don't know if that could help, but if I understood your issue, you have a lot of documents with the same or very close scores. Moreover I think you get your matches in Merchant order (more or less) because they must be indexed in that very same order, so solr returns documents of same sco

[jira] [Commented] (LUCENENET-502) Recreate the missing files needed to build Lucene.Net.Distributed

[ https://issues.apache.org/jira/browse/LUCENENET-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437960#comment-13437960 ] Zachary Gramana commented on LUCENENET-502: --- My recommendation is to commit t

Re: [jira] [Commented] (SOLR-3674) PathHierarchyTokenizerFactory needs better docs, tests, and example config

The best documentation for anything like this is always the admin/analysis page. It'll show you all the tokens that get put into the index and the tokens that are part of the query. And, as always, any improvements to the docs you can make are welcome. Best Erick On Mon, Aug 20, 2012 at 9:45 AM,

Re: Compilation issues

You shouldn't have to add anything like that. Try taking your new additions to the classpath out and executing 'ant clean clean-jars', then 'ant resolve' then build... The other possibility is that you have some "odd" jars already in your classpath, but all the jars you need should be in the Solr

[jira] [Commented] (SOLR-3674) PathHierarchyTokenizerFactory needs better docs, tests, and example config

[ https://issues.apache.org/jira/browse/SOLR-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437951#comment-13437951 ] Mandar commented on SOLR-3674: -- I am trying to use HierarchicalFaceting described at http://w

[jira] [Updated] (SOLR-2366) Facet Range Gaps

[ https://issues.apache.org/jira/browse/SOLR-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar updated SOLR-2366: - Comment: was deleted (was: Thanks, I am also trying to use HierarchicalFaceting described at http://wiki.apache.o

Re: Compilation issues

On 20/08/2012 17:28, Itamar Syn-Hershko wrote: Hi there, Hi Itamar, I checked out trunk, but can't get it to compile. I just updated my working copy and `ant compile` works fine. What command or IDE are you using to build Lucene/Solr ? -- Adrien Grand ---

[jira] [Commented] (SOLR-2366) Facet Range Gaps

[ https://issues.apache.org/jira/browse/SOLR-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437947#comment-13437947 ] Mandar commented on SOLR-2366: -- Thanks, I am also trying to use HierarchicalFaceting described

Compilation issues

Hi there, I checked out trunk, but can't get it to compile. I'm getting package / import errors in the following files: \lucene\tools\src\java\org\apache\lucene\validation\ForbiddenApisCheckTask.java \lucene\test-framework\src\java\org\apache\lucene\codecs\asserting\AssertingCodec.java \lucene\t

Re: twitter questions

Get MetroTwit or TwitDeck and create your own Twitter account while at it :) On Mon, Aug 20, 2012 at 5:52 PM, Prescott Nasser wrote: > I'm terrible with social media- is there any way to have tweets directed > at @LuceneDotNet sent to one of our mailing lists? Or should I just get on > top of mon

[jira] [Commented] (LUCENE-4315) Minor fixes for Fields abstract class, TermVectorsWriter

[ https://issues.apache.org/jira/browse/LUCENE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437916#comment-13437916 ] Robert Muir commented on LUCENE-4315: - I agree with the patch. On a related note, w

Re: twitter questions

Some useful links for those that want to find unanswered questions about Lucene.NET on Stack Overflow: Newest unclosed, unanswered tagged [lucene.net]:http://stackoverflow.com/search?tab=newest&q=%5blucene.net%5d%20closed%3a0%20answers%3a0 Newest unclosed,

RE: twitter questions

I'm terrible with social media- is there any way to have tweets directed at @LuceneDotNet sent to one of our mailing lists? Or should I just get on top of monitoring it more often? > From: casper...@caspershouse.com > To: lucene-net-...@lucene.apache.org > CC: lucene-net-...@lucene.apache.org >

[jira] [Updated] (LUCENE-4315) Minor fixes for Fields abstract class, TermVectorsWriter

[ https://issues.apache.org/jira/browse/LUCENE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-4315: -- Description: The Fields abstract class is a little bit inconsistent. It does not allow iterat

[jira] [Updated] (LUCENE-4315) Minor fixes for Fields abstract class, TermVectorsWriter

[ https://issues.apache.org/jira/browse/LUCENE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-4315: -- Attachment: LUCENE-4315.patch Patch. This patch also removes oal.util.UnmodifiableIterator. T

[jira] [Commented] (LUCENE-4311) HunspellStemFilter returns another values than Hunspell in console / command line with same dictionaries.

[ https://issues.apache.org/jira/browse/LUCENE-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437912#comment-13437912 ] Chris Male commented on LUCENE-4311: Hey Jan, I will take a look at this and see if

[jira] [Created] (LUCENE-4315) Minor fixes for Fields abstract class, TermVectorsWriter

Uwe Schindler created LUCENE-4315: - Summary: Minor fixes for Fields abstract class, TermVectorsWriter Key: LUCENE-4315 URL: https://issues.apache.org/jira/browse/LUCENE-4315 Project: Lucene - Core

Re: twitter questions

Answered: http://stackoverflow.com/a/12039811/50776 On Aug 20, 2012, at 10:42 AM, "Michael Herndon" wrote: > Thanks Nicholas for having a look at the SO question. Anyone know > about the NIOFSDirectory off the top of their head? > > Cheers, > Michael > > > > On Mon, Aug 20, 2012 at 10:28

  1   2   >