On Saturday, November 12, 2005, at 05:37PM, Chris Hostetter <[EMAIL PROTECTED]>
wrote:
>if the fields you are talking
>about "sharing" are allways indexed, then you can leave them UnStored, and
>use a FieldCache.StringIndex to get the values.
This is a great suggestion except that the terms store
Mark et al,
I'm delving into highlighting text (per-field, like the recent topic
on java-user) and need it to highlight the exact spots used in the
query, not just all query terms as the current Highlighter does. And
I need it to be SpanQuery savvy. Further, it seems the Spans
capabilit
The first thing that occurs to me, is that if the fields you are talking
about "sharing" are allways indexed, then you can leave them UnStored, and
use a FieldCache.StringIndex to get the values.
-Hoss
-
To unsubscribe, e-mai
Hi Dave,
I've looked at your Ferret project. Great work!
I've browsed somewhat through the C-code,
looks quite familiar to me. What were the problems
you've mentioned in your mail? I may not have
noticed them, perhaps it could help us make the
code better if we shared ideas.
If you're interested
Would the following be a reasonable feature to add to Lucene?
We use Lucene for a catalog with about 3 million items, each document
represents one item. Some Fields are highly redundant, such as "Manufacturer
Name"; we only have a few hundred different manufacturers. I would like to be
able d
On 12 Nov 2005, at 06:15, Paul Elschot wrote:
I upgraded ant and building from contrib/surround/build.xml works
here.
However
ant build-contrib
using the lucene build.xml currently fails at compiling the lucene
test code.
Help me out here... the error message please :)
At revision 33275
On 12 Nov 2005, at 05:43, Daniel Naber wrote:
On Samstag 12 November 2005 10:03, [EMAIL PROTECTED] wrote:
+23. Added regular expression queries, RegexQuery and SpanRegexQuery.
+Note the same term enumeration caveats apply with these
queries as
+apply to WildcardQuery and other ter
Hello experts,
sorry for cross posting but this is really important for me. For
documentation purposes I need to know the exact scoring formula that is used
by the Lucene 1.2 release. I have found a scoring formula in the Lucene book
but this is likely oriented on the 1.4 release and might have ch
On Saturday 12 November 2005 10:55, Erik Hatcher wrote:
>
> On 12 Nov 2005, at 04:41, Paul Elschot wrote:
> >> Could you try using Ant 1.6.5? I just built contrib/surround
> >>
> >
> > The joy of developing at the cutting edge...
>
> Was the upgrade of Ant what fixed it?
I also reverted all bu
On Samstag 12 November 2005 10:03, [EMAIL PROTECTED] wrote:
> +23. Added regular expression queries, RegexQuery and SpanRegexQuery.
> + Note the same term enumeration caveats apply with these queries as
> + apply to WildcardQuery and other term expanding queries.
Maybe you should add that t
On 12 Nov 2005, at 04:41, Paul Elschot wrote:
Could you try using Ant 1.6.5? I just built contrib/surround
The joy of developing at the cutting edge...
Was the upgrade of Ant what fixed it?
I upgraded ant and building from contrib/surround/build.xml works
here.
However
ant build-cont
On Saturday 12 November 2005 02:12, Erik Hatcher wrote:
>
> On 11 Nov 2005, at 17:26, Paul Elschot wrote:
> >> Paul - what version of Ant are you using? I'm (always) swamped, but
> >> I'll put this on my list of things to look at as soon as possible if
> >> no one else beats me to it.
> >>
> >
>
[ http://issues.apache.org/jira/browse/LUCENE-461?page=all ]
Erik Hatcher closed LUCENE-461:
---
> StandardTokenizer splitting all of Korean words into separate characters
>
>
>
[ http://issues.apache.org/jira/browse/LUCENE-461?page=all ]
Erik Hatcher resolved LUCENE-461:
-
Fix Version: 1.9
Resolution: Fixed
These patches have been applied, thanks!
There is one thing to note, and that is a change in the token type emi
14 matches
Mail list logo
