The common problem with native logging, log4j and slf4j (logback impl)
is that they are totally unsuitable for actually logging something.
They do good work checking if the logging can be avoided, but use
almost-global locking if you really try to write this line to a file.
My research shows there
On thinking more about this... I think with a few small changes we
could achieve Sort by field without materializing a full array. We
can decouple this change from LUCENE-831.
I think all that's needed is:
* Expose sub-readers (LUCENE-1475) by adding IndexReader[]
IndexReader.getSubReade
On Dec 8, 2008, at 6:15 AM, Michael McCandless wrote:
I don't see this. When I "ls -l --time-style=full-iso" these files:
-rw-rw-rw- 1 mike users 20796 2008-11-26 05:25:28.0 -0500
src/demo/org/apache/lucene/demo/html/HTMLParser.java
-rw-rw-rw- 1 mike users 9486 2008-11-26 05:25:28
I don't see this. When I "ls -l --time-style=full-iso" these files:
-rw-rw-rw- 1 mike users 20796 2008-11-26 05:25:28.0 -0500 src/
demo/org/apache/lucene/demo/html/HTMLParser.java
-rw-rw-rw- 1 mike users 9486 2008-11-26 05:25:28.0 -0500 src/
demo/org/apache/lucene/demo/html/H
What do we get from this though? A MultiSearcher (with the scoring
issues) that can properly do rewrite? Won't we have to take
MultiSearchers scoring baggage into this as well?
Michael McCandless wrote:
On thinking more about this... I think with a few small changes we
could achieve Sort by
Mark Miller wrote:
What do we get from this though? A MultiSearcher (with the scoring
issues) that can properly do rewrite? Won't we have to take
MultiSearchers scoring baggage into this as well?
If this can work, what we'd get is far better reopen() performance
when you sort-by-field, wi
[
https://issues.apache.org/jira/browse/LUCENE-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654410#action_12654410
]
Mck SembWever commented on LUCENE-1380:
---
ping. are there any committors willing to c
Michael McCandless wrote:
Mark Miller wrote:
What do we get from this though? A MultiSearcher (with the scoring
issues) that can properly do rewrite? Won't we have to take
MultiSearchers scoring baggage into this as well?
If this can work, what we'd get is far better reopen() performance
w
[
https://issues.apache.org/jira/browse/LUCENE-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654413#action_12654413
]
Michael McCandless commented on LUCENE-831:
---
bq. It seems with this field cache
{quote}
My research shows there are no ready-made java logging frameworks that can
be used in high-load production environment.
{quote}
I'm not sure I understand what you mean by that. We use Java logging in our
high-profiled products, which support 100s of tps. Logging is usually turned
off, and
[
https://issues.apache.org/jira/browse/LUCENE-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654417#action_12654417
]
Uwe Schindler commented on LUCENE-831:
--
{quote}This is an interesting idea. Say we cre
[
https://issues.apache.org/jira/browse/LUCENE-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654418#action_12654418
]
Robert Newson commented on LUCENE-831:
--
Yes, something like that. I made a Document c
[
https://issues.apache.org/jira/browse/LUCENE-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654417#action_12654417
]
thetaphi edited comment on LUCENE-831 at 12/8/08 6:04 AM:
---
{q
[
https://issues.apache.org/jira/browse/LUCENE-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Newson updated LUCENE-831:
-
Attachment: ExtendedDocument.java
Type-safe Document-style object. Doesn't extend Document as it
Replace infoSteram by a logging framework (SLF4J)
-
Key: LUCENE-1482
URL: https://issues.apache.org/jira/browse/LUCENE-1482
Project: Lucene - Java
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/LUCENE-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-1482:
---
Attachment: LUCENE-1482.patch
This patch covers:
- Using SLF4J in all the classes that used infoStre
On Sat, Dec 6, 2008 at 11:52 AM, Shai Erera <[EMAIL PROTECTED]> wrote:
> On the performance side, I don't expect to see any different performance
> than what we have today, since checking if infoStream != null should be
> similar to logger.isLoggable (or the equivalent methods from SLF4J).
I'm lee
Mark Miller wrote:
Michael McCandless wrote:
Mark Miller wrote:
What do we get from this though? A MultiSearcher (with the
scoring issues) that can properly do rewrite? Won't we have to
take MultiSearchers scoring baggage into this as well?
If this can work, what we'd get is far bette
[
https://issues.apache.org/jira/browse/LUCENE-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654434#action_12654434
]
Michael McCandless commented on LUCENE-1481:
Patch looks good; I'll commit sho
[
https://issues.apache.org/jira/browse/LUCENE-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1481.
Resolution: Fixed
Fix Version/s: 2.9
Lucene Fields: [New, Patch Availabl
[
https://issues.apache.org/jira/browse/LUCENE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1478:
--
Attachment: LUCENE-1478.patch
As LUCENE-1481 is committed, here the updated patch with SortFie
I referred to the case when you want normal production logs, like
access logs, or whatever.
Debugging with all common logging implementations is also broken,
because switching logging on/off dramatically changes multithreading
picture.
On Mon, Dec 8, 2008 at 17:02, Shai Erera <[EMAIL PROTECTED]> w
I tried a quick poor mans version using a MultiSearcher and wrapping the
sub readers as searchers. Other than some AUTO sort field detection
problems, all tests do appear to pass. The new sort stuff for
MultiSearcher may be a tiny bit off...sort tests fail, though are only
slightly off, with th
Mark Miller wrote:
I tried a quick poor mans version using a MultiSearcher and wrapping
the sub readers as searchers. Other than some AUTO sort field
detection problems, all tests do appear to pass.
Excellent, that sounds like a tentatively positive result, though we
do need to get to th
Michael McCandless wrote:
Mark Miller wrote:
I tried a quick poor mans version using a MultiSearcher and wrapping
the sub readers as searchers. Other than some AUTO sort field
detection problems, all tests do appear to pass.
Excellent, that sounds like a tentatively positive result, though
Hi Mark,
> I'm going to dig in more tonight I hope. The main issue is that using
> SortType.AUTO blows up because the MultiSearcher code expects it already
> to have been resolved to a sort type, but my hack kept that from
> happening so it hits a switch statement for AUTO that throws an
> excepti
[
https://issues.apache.org/jira/browse/LUCENE-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654488#action_12654488
]
Jason Rutherglen commented on LUCENE-831:
-
M. McCandless:
"This is an interesting
[
https://issues.apache.org/jira/browse/LUCENE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1478:
---
Attachment: LUCENE-1478.patch
OK I made a few small changes to the patch: added CHAN
[
https://issues.apache.org/jira/browse/LUCENE-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654513#action_12654513
]
Doug Cutting commented on LUCENE-1473:
--
Would it take any more lines of code to remov
[
https://issues.apache.org/jira/browse/LUCENE-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated LUCENE-1475:
-
Attachment: LUCENE-1475.patch
LUCENE-1475.patch
- Added getSubReaders to IndexReader wh
[
https://issues.apache.org/jira/browse/LUCENE-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1471:
--
Assignee: Michael McCandless
> Faster MultiSearcher.search merge docs
> -
[
https://issues.apache.org/jira/browse/LUCENE-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654518#action_12654518
]
robert engels commented on LUCENE-1475:
---
I think the API is wrong.
The method shoul
[
https://issues.apache.org/jira/browse/LUCENE-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654520#action_12654520
]
Michael McCandless commented on LUCENE-1471:
I agree performance improvement
[
https://issues.apache.org/jira/browse/LUCENE-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654529#action_12654529
]
Jason Rutherglen commented on LUCENE-1471:
--
The patches seem to implement the sam
[
https://issues.apache.org/jira/browse/LUCENE-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654532#action_12654532
]
Michael McCandless commented on LUCENE-1475:
I agree: a better default impl is
[
https://issues.apache.org/jira/browse/LUCENE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654537#action_12654537
]
Uwe Schindler commented on LUCENE-1478:
---
Hi Mike,
patch looks good, checked each ch
[
https://issues.apache.org/jira/browse/LUCENE-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654546#action_12654546
]
Michael McCandless commented on LUCENE-1471:
bq. The patches seem to implement
[
https://issues.apache.org/jira/browse/LUCENE-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654545#action_12654545
]
Doug Cutting commented on LUCENE-1482:
--
> Should I attach the slf4j jars separately?
[
https://issues.apache.org/jira/browse/LUCENE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654537#action_12654537
]
thetaphi edited comment on LUCENE-1478 at 12/8/08 11:59 AM:
[
https://issues.apache.org/jira/browse/LUCENE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1478:
---
Attachment: LUCENE-1478.patch
New patch attached:
bq. Maybe you should add the pars
[
https://issues.apache.org/jira/browse/LUCENE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654569#action_12654569
]
Uwe Schindler commented on LUCENE-1478:
---
Hi Mike,
all is ok. The extra check is bett
[
https://issues.apache.org/jira/browse/LUCENE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654571#action_12654571
]
Michael McCandless commented on LUCENE-1476:
I like this approach!!
It's als
[
https://issues.apache.org/jira/browse/LUCENE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1478.
Resolution: Fixed
Lucene Fields: [New, Patch Available] (was: [Patch Availa
[
https://issues.apache.org/jira/browse/LUCENE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1478:
---
Lucene Fields: [New, Patch Available] (was: [Patch Available, New])
Fix Version/
That sounds much better. Trying to distribute lucene (my reason why all this
would be interesting) itself is just not going to work for far too many
applications and will put burden on API extensions.
My point is, I do not want to distribute Lucene Index, I need to distribute my
application tha
I think an important piece to make this work is the query parser/syntax.
We already have a system similar to what is outlined below. We made
changes to the query syntax to support our various query extensions.
The nice thing, is that persisting queries is a simple string. It
also makes it
[
https://issues.apache.org/jira/browse/LUCENE-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654589#action_12654589
]
Grant Ingersoll commented on LUCENE-1462:
-
Karl,
I made TVOI serializable: Commit
[
https://issues.apache.org/jira/browse/LUCENE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654592#action_12654592
]
Jason Rutherglen commented on LUCENE-1476:
--
Marvin:
"I'm also bothered by the pr
[
https://issues.apache.org/jira/browse/LUCENE-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated LUCENE-1471:
-
Comment: was deleted
> Faster MultiSearcher.search merge docs
> ---
[
https://issues.apache.org/jira/browse/LUCENE-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654594#action_12654594
]
Jason Rutherglen commented on LUCENE-1471:
--
Wouldn't it be good to remove BitVect
[
https://issues.apache.org/jira/browse/LUCENE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654595#action_12654595
]
Jason Rutherglen commented on LUCENE-1476:
--
Wouldn't it be good to remove BitVect
Well, there's the pretty sophisticated and extensible XML query parser
in contrib. I've still only scratched the surface of it, but it meets
the specs you mentioned.
Erik
On Dec 8, 2008, at 4:51 PM, robert engels wrote:
I think an important piece to make this work is the query par
The problem with that is that in most cases you still need a "string"
based syntax that "people" can enter...
I guess you can always have an "advanced search" page that builds and
submits the XML query behind the scenes.
On Dec 8, 2008, at 4:40 PM, Erik Hatcher wrote:
Well, there's the p
Building your own parser with Antlr is really easy. Using Ragel is
harder, but yields insane parsing performance.
Is there any reason to worry about library-bundled parsers if you're
making something more complex then a college project?
On Tue, Dec 9, 2008 at 01:49, robert engels <[EMAIL PROTECTED
[
https://issues.apache.org/jira/browse/LUCENE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1478:
--
Attachment: LUCENE-1478-cleanup.patch
Hi Mike,
sorry, after looking a second time into the new
I only meant is from a persistence standpoint - if you need a full
"human enterable" query syntax anyway, why not just use that as the
persistence format.
On Dec 8, 2008, at 4:53 PM, Earwin Burrfoot wrote:
Building your own parser with Antlr is really easy. Using Ragel is
harder, but yields
Mark Miller wrote:
Which new sort stuff are you referring to? Is it LUCENE-1471?
Yes. First thing I did was try and patch this in, but the sort tests
failed. It would be the right order, but like the two center docs
would be reversed or something. No time to dig in, so I just switch to
the
Hi Mark,
> Thanks for the ref to that bug Uwe, was indeed the problem.
This is now committed: updates in FieldSortedHitQueue, new super-interface
for FieldCache.Parsers and SortField changes (see Mikes commit as I have no
committer status yet).
Uwe
-
The problem with that is that in most cases you still need a "string"
based syntax that "people" can enter...
The XML syntax includes a tag for embedding user input of
this type.
I guess you can always have an "advanced search" page that builds and
submits the XML query behind the scenes.
[
https://issues.apache.org/jira/browse/LUCENE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654637#action_12654637
]
Michael McCandless commented on LUCENE-1478:
No problem -- Committed revision
Mark Miller wrote:
Mark Miller wrote:
Which new sort stuff are you referring to? Is it LUCENE-1471?
Yes. First thing I did was try and patch this in, but the sort
tests failed. It would be the right order, but like the two center
docs would be reversed or something. No time to dig in,
[
https://issues.apache.org/jira/browse/LUCENE-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-1435:
Attachment: LUCENE-1435.patch
Removed accidentally included IndexableBinaryString and its test fro
Change IndexSearcher to use MultiSearcher semantics for sorted searches
---
Key: LUCENE-1483
URL: https://issues.apache.org/jira/browse/LUCENE-1483
Project: Lucene - Java
Is
Michael McCandless wrote:
Mark Miller wrote:
Mark Miller wrote:
Which new sort stuff are you referring to? Is it LUCENE-1471?
Yes. First thing I did was try and patch this in, but the sort tests
failed. It would be the right order, but like the two center docs
would be reversed or somet
Mark Miller wrote:
Mark Miller wrote:
Which new sort stuff are you referring to? Is it LUCENE-1471?
Yes. First thing I did was try and patch this in, but the sort tests
failed. It would be the right order, but like the two center docs
would be reversed or something. No time to dig in, so I
[
https://issues.apache.org/jira/browse/LUCENE-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654712#action_12654712
]
Luke Nezda commented on LUCENE-1471:
I will prepare a similar derivative patch that co
[
https://issues.apache.org/jira/browse/LUCENE-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654720#action_12654720
]
Luke Nezda commented on LUCENE-1471:
* Simplified MultiSearcherThread
** Pulled out r
[
https://issues.apache.org/jira/browse/LUCENE-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Nezda updated LUCENE-1471:
---
Attachment: multisearcher.take2.patch
Patch covering MultiSearcher and ParallelMultiSearcher
> Fast
68 matches
Mail list logo
