Responding to the thread as a whole, having read it with great interest.
I'd be interested to know what packagers for distributions such as
debian and fedora do with systems that patch 3rd party dependencies.
I'll guess that if it is internalized as mentioned below that there is
no problem.
[
https://issues.apache.org/jira/browse/LUCENE-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258348#comment-13258348
]
DM Smith commented on LUCENE-3977:
--
Personally I'd like them not to be in t
Thanks!
On Apr 17, 2012, at 7:19 PM, Jan Høydahl wrote:
> Same happened here. The installer removes 1.5 and 1.5.0 folders and replaces
> with softlink to the new JDK.
> Luckily I named my 1.5 JDK as 1.5.0_30 so it was still there, the only thing
> needed was add the softlinks.
>
> sudo su
> c
On 03/16/2012 05:04 AM, Dawid Weiss wrote:
So close!
https://blogs.oracle.com/henrik/entry/updated_java_6_eol_date?msgid=3-6077692575
Dawid
It's only close as a date. It is rather far away in practice. It is
developer only at this point.
Also, they are working on a Mac version, but I doubt
[
https://issues.apache.org/jira/browse/LUCENE-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223298#comment-13223298
]
DM Smith commented on LUCENE-3747:
--
A release candidate is avail
[
https://issues.apache.org/jira/browse/LUCENE-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223294#comment-13223294
]
DM Smith commented on LUCENE-1799:
--
Would someone be able to champion this. It app
[
https://issues.apache.org/jira/browse/LUCENE-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212003#comment-13212003
]
DM Smith commented on LUCENE-3806:
--
Regarding image vs txt, an image is harde
I haven't tried the trunk/4.0 stuff, so maybe I'm out of line, but how about a
public alpha first. It would have appropriate disclaimers regarding quality and
that the API, while reasonably stable, is subject to change w/ little notice.
I tink beta implies that there is a high degree of confiden
How about an issue to track this? I'd be glad to do it, but I'm not
really the "reporter" for it.
-- DM
On 12/20/2011 09:51 AM, Shai Erera wrote:
Thanks for the clarification Uwe. If the whole idea is a new RAMDirectory
implementation, that is more efficient, then it's ok. I think that the
ide
[
https://issues.apache.org/jira/browse/LUCENE-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172578#comment-13172578
]
DM Smith edited comment on LUCENE-3653 at 12/19/11 8:2
[
https://issues.apache.org/jira/browse/LUCENE-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172578#comment-13172578
]
DM Smith commented on LUCENE-3653:
--
bq. In fact we were talking here about searc
[
https://issues.apache.org/jira/browse/LUCENE-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172446#comment-13172446
]
DM Smith commented on LUCENE-3653:
--
bq. Thats a hard to eliminate misbelief - same
Just a thought:
One way to maintain backward compatibility would be to have a two stage parser.
The first stage does the breaking of the input on keywords. The second does the
rest of the work that the current qp does. Those that want to have the old
behavior use both stages, but those that wan
+1 please fix the QP bug. It should only identify query keywords and
non-keywords.
On Oct 26, 2011, at 8:09 AM, Robert Muir wrote:
> Use a queryparser that doesnt break on whitespace as a workaround?
> Or, we can start thinking about how to fix QueryParser
> (https://issues.apache.org/jira/b
[
https://issues.apache.org/jira/browse/LUCENE-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133683#comment-13133683
]
DM Smith commented on LUCENE-3301:
--
Robert, do you know why the bug you provided
[
https://issues.apache.org/jira/browse/LUCENE-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114304#comment-13114304
]
DM Smith commented on LUCENE-3454:
--
When I started w/ Lucene, I read the docs and
You'll get more responses if you ask on the user's list. This list is for the
development of the Lucene library, not for user application of the library.
On Jul 5, 2011, at 6:42 PM, jcardona7508 wrote:
> Hi everybody, I have a question, I need a to create documents with two words
> terms, for e
+1 from old-stick-in-the-mud, whose vote does not count :)
BTW, today Apple released Java 1.5.0_30. So while Oracle has not
supplied security updates or bug fixes to 1.5 since Nov 2009, except to
premier customers, Apple is still actively supporting it for OS X 10.5,
Leopard.
On 06/28/2011 1
[
https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054735#comment-13054735
]
DM Smith commented on LUCENE-3239:
--
Same page.
> drop java 5 &
[
https://issues.apache.org/jira/browse/LUCENE-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054621#comment-13054621
]
DM Smith commented on LUCENE-3239:
--
Hey, it's me, old-stick-in-the-mud, wrt
On 06/21/2011 02:01 PM, johnmu...@aol.com wrote:
My bad, I meant to say a “6-8 releases a year” .. grrr!!
So let me try this again. I don't like the current plan of "release
early & often" because:
1) It will spread testing thin of any release because fewer real users
will be using a release w
What is the bug? I have an interest in this component and am willing to
see about fixing it. It appears that it is a Javadoc bug??? Why would we
keep good code out for that?
-- DM
On 04/15/2011 09:15 AM, Steven A Rowe wrote:
As a result of Robert Muir's r1092398 commit on branch_3x (the Latvi
On Mar 17, 2011, at 11:05 PM, Chris Hostetter wrote:
>
> : The source is because I *think* we are required by the ASF to have
>
> yes. we are.
Two thoughts on src distribution:
Linux distributions, such as RedHat & Debian, have a policy of building from
pristine source. They want the official
On Mar 10, 2011, at 9:18 PM, Chris Hostetter wrote:
> i'm just wondering if we really need both lucene-src and
> solr-src artifacts. particularly considering that solr-src is already a
> superset of lucene-src ... it just seems like one uber lucene-solr-src
> package of the "dev" tree would
On 02/15/2011 02:07 PM, Robert Muir wrote:
On Tue, Feb 15, 2011 at 1:33 PM, Mark Miller wrote:
It appears to me, that the effort to commit the contributions are minimal, and
that in this case the true cost is that of doing the release.
Heh. I think looks can be deceiving sometimes. I'm not su
lp scratch your itch is the best advice I can give.
- Mark
On Feb 15, 2011, at 11:04 AM, Bill Bell wrote:
I would love to see a release every 3 to 6 months too
Bill Bell
Sent from mobile
On Feb 15, 2011, at 8:55 AM, DM Smith wrote:
Can we see more frequent releases? Can we look forward to a 3
Can we see more frequent releases? Can we look forward to a 3.2 release
in a few months? Say May 15? That'd be a "quarterly" release cycle.
(Personally, I'd like to see Robert's improvement to the handling of
Chinese as soon as possible.)
-- DM
On 02/15/2011 10:24 AM, Robert Muir wrote:
On Tue
[
https://issues.apache.org/jira/browse/LUCENE-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991170#comment-12991170
]
DM Smith commented on LUCENE-1799:
--
Any idea as to when this will be rele
[
https://issues.apache.org/jira/browse/LUCENE-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991169#comment-12991169
]
DM Smith commented on LUCENE-2906:
--
Two questions:
How will this differ from
, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>> -Original Message-
>> From: DM Smith [mailto:dm-sm...@woh.rr.com]
>> Sent: Sunday, December 05, 2010 12:16 AM
>> To: dev@lucene.apache.org
>> Subject: Exception in migrating from 2.9.x to 3.
The current code that works on Android with 2.9.1, but fails with 3.0.2:
Directory dir = FSDirectory.open(file);
...
do something with directory
...
The error we're seeing is:
12-04 21:34:41.629: WARN/System.err(23160): java.lang.NoClassDefFoundError:
java.lang.management.ManagementFactory
12-04
[
https://issues.apache.org/jira/browse/LUCENE-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966540#action_12966540
]
DM Smith commented on LUCENE-2791:
--
I've just back ported all the code to Java
[
https://issues.apache.org/jira/browse/LUCENE-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965575#action_12965575
]
DM Smith commented on LUCENE-2786:
--
I bet it is there for mixed language texts.
I'm curious about somethings in the ThaiAnalyzer
It has:
@Override
public TokenStream reusableTokenStream(String fieldName, Reader reader)
throws IOException {
if (overridesTokenStreamMethod) {
// LUCENE-1678: force fallback to tokenStream() if we
// have been subclassed and t
On 11/29/2010 03:43 PM, Earwin Burrfoot wrote:
On Mon, Nov 29, 2010 at 20:51, DM Smith wrote:
The other thing I'd like is for the spec to be save along side of the index
as a manifest. From earlier threads, I can see that there might need to be
one for writing and another for reading. I&
On 11/29/2010 01:43 PM, Robert Muir wrote:
On Mon, Nov 29, 2010 at 12:51 PM, DM Smith wrote:
Instead, you should use a Tokenizer that respects canonical
equivalence (tokenizes text that is canonically equivalent in the same
way), such as UAX29Tokenizer/StandardTokenizer in branch_3x. Ideally
On 11/29/2010 01:03 PM, Robert Muir wrote:
On Mon, Nov 29, 2010 at 12:51 PM, DM Smith wrote:
I'd have to look to be sure: IIRC, Turkish was one. The treatment of 'i' was
buggy. Russian had it's own encoding that was replaced with UTF-8. The
QueryParser had bug fixes. The
On 11/29/2010 09:40 AM, Robert Muir wrote:
On Mon, Nov 29, 2010 at 9:05 AM, DM Smith wrote:
In my project, I don't use any of the Analyzers that Lucene provides, but I
have variants of them. (Mine allow take flags indicating whether to filter stop
words and whether to do stemming)
On Nov 29, 2010, at 5:34 AM, Robert Muir wrote:
> On Mon, Nov 29, 2010 at 2:50 AM, Earwin Burrfoot wrote:
>> And for indexes:
>> * Index compatibility is guaranteed across two adjacent major
>> releases. eg 2.x -> 3.x, 3.x -> 4.x.
>> That includes both binary compat - codecs, and semantic compa
[
https://issues.apache.org/jira/browse/LUCENE-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930690#action_12930690
]
DM Smith commented on LUCENE-2747:
--
Robert, I think
* "core" is a bad name
[
https://issues.apache.org/jira/browse/LUCENE-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930670#action_12930670
]
DM Smith commented on LUCENE-2747:
--
Robert/Steven, I'm sorry. I fat fingered
[
https://issues.apache.org/jira/browse/LUCENE-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930578#action_12930578
]
DM Smith commented on LUCENE-2747:
--
{quote}
bq. Shouldn't UAX29Tokenizer be
[
https://issues.apache.org/jira/browse/LUCENE-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930585#action_12930585
]
DM Smith commented on LUCENE-2747:
--
Robert, Let me ask another way. How a
[
https://issues.apache.org/jira/browse/LUCENE-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930448#action_12930448
]
DM Smith commented on LUCENE-2747:
--
Robert, I think we are on the same wavele
[
https://issues.apache.org/jira/browse/LUCENE-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930119#action_12930119
]
DM Smith commented on LUCENE-2747:
--
bq. DM, can you elaborate here?
I was a bit tri
[
https://issues.apache.org/jira/browse/LUCENE-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929934#action_12929934
]
DM Smith commented on LUCENE-2747:
--
I'm not too keen on this. For classics an
On Oct 30, 2010, at 12:00 PM, Robert Muir wrote:
> On Sat, Oct 30, 2010 at 11:54 AM, Yonik Seeley
> wrote:
>> If it's only for the QP, a simple method that one could override would
>> suffice:
>> QueryParser.getTokenStream(String field, String value)
>>
>> If it's not just for the QP, then we
On Oct 30, 2010, at 10:49 AM, Uwe Schindler wrote:
> we should not have analyzers at all (just my personal opinion)
+1 It should be sufficient to document order of their parts. They could be
constructed from a spec using reflection.
-
On Oct 19, 2010, at 12:20 PM, Robert Muir wrote:
> On Tue, Oct 19, 2010 at 12:17 PM, DM Smith wrote:
>
>> I'd be surprised if there are use cases for non-reuse.
>>
>> IIRC: When we started down the reuse path, the goal was reuse only, not just
>> reuse by
On Oct 19, 2010, at 12:20 PM, Robert Muir wrote:
> On Tue, Oct 19, 2010 at 12:17 PM, DM Smith wrote:
>
>> I'd be surprised if there are use cases for non-reuse.
>>
>> IIRC: When we started down the reuse path, the goal was reuse only, not just
>> reuse by
On Oct 19, 2010, at 11:21 AM, Robert Muir wrote:
> On Tue, Oct 19, 2010 at 11:10 AM, Shai Erera wrote:
>> Is there real danger in having my analyzer not declaring these methods final
>> - something that can affect Lucene code for example? Or am I only risking my
>> code?
>>
>
> There is a real
On Jun 25, 2010, at 5:15 PM, Robert Muir wrote:
>
> i just got a new mac too, and it doesn't support java 5, so lets [lucene,
> too!] please move away from forrest!!!
You can get and install java 1.5 on snow leopard. I don't remember what I did
to get it. Found it via google.
--DM
---
[
https://issues.apache.org/jira/browse/LUCENE-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868230#action_12868230
]
DM Smith commented on LUCENE-2167:
--
{quote}
bq.Naming will require some thought, th
[
https://issues.apache.org/jira/browse/LUCENE-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866954#action_12866954
]
DM Smith commented on LUCENE-2458:
--
As I see it there are two issues:
1) Back
Assuming that the vote passed: I'm wondering where this leaves us for
the near term? How it works in practice.
There have been a lot of recent changes and flex has landed. There are a
bunch of issues marked as 3.1 and many (most?) have decent patches.
Let's suppose a 3.1 release soon. What wo
On 04/26/2010 02:43 PM, Chris Hostetter wrote:
I didn't follow the Version API relaxation thread (my fault: i thought it
was focused solely on how we were dealing with o.a.l.Version and lots of
smart people were talking in ernest so i left it to them to make smart
choices) but looking at this pro
On Apr 25, 2010, at 4:10 PM, Shai Erera wrote:
> I think that we agree in principal about the policy change. We seem to
> disagree only on where should the default dev should be: trunk or
> branch.
I don't think it matters. Just document the decision in the wiki in a
Development Roadmap. Maybe
Having read the entire thread as it's come in, my head is spinning. It is hard
to keep up with the ideas and proposals. Through out this thread my mindset has
changed, more than once. And may change again ;)
To that end I'd like to make some end-user observations and thoughts:
(I had thought tha
[
https://issues.apache.org/jira/browse/LUCENE-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859995#action_12859995
]
DM Smith commented on LUCENE-2413:
--
Robert: +1
> Consolidate all (Solr'
59 matches
Mail list logo
