Mike,
That's an interesting idea. The only drawback is we have to re-parse the
doc and find where it matches and what the associated values are. It could
be a performance issue if the doc becomes bigger and more complex.
I am wondering if there is a way to index a value a1 for a field A and
store
On 10/02/2013 07:12 PM, Alice Wong wrote:
Hello,
We would like to index some documents. Each field of a document may have
multiple values. And for each (field,value) pair there are some associated
values. These associated values are just for retrieving, not searching.
For example, a document D
Hi folks,
Here's a small tool that I'm releasing as open source. I hope some of
you might find it useful:
https://github.com/joelb-git/lqt
Lucene Query Tool (lqt) is a small utility for executing and
formatting Lucene queries from the command line (rather from inside a
graphical tool like Luke)
Thanks for your Reply Ian.
I will check and let you know.
On Thu, Oct 3, 2013 at 9:19 PM, Ian Lea wrote:
> Below is a little self-contained test program. You may recognise some
> of the code.
>
> Here's the output from a couple of runs using lucene 4.4.0.
>
> $ java ian.G1 "Dremel is a scalab
Below is a little self-contained test program. You may recognise some
of the code.
Here's the output from a couple of runs using lucene 4.4.0.
$ java ian.G1 "Dremel is a scalable, interactive ad-hoc query system"
"interactive ad-hoc"
term=interactive
term=ad-hoc
+content:"interactive" +content:"
Hi,
sorry.. thats my typo..
Its not failing because of that
On Thu, Oct 3, 2013 at 8:17 PM, Ian Lea wrote:
> Are you sure it's not failing because "adhoc" != "ad-hoc"?
>
>
> --
> Ian.
>
>
> On Thu, Oct 3, 2013 at 3:07 PM, VIGNESH S wrote:
> > Hi,
> >
> > I am Trying to do Multiphrase Query i
Are you sure it's not failing because "adhoc" != "ad-hoc"?
--
Ian.
On Thu, Oct 3, 2013 at 3:07 PM, VIGNESH S wrote:
> Hi,
>
> I am Trying to do Multiphrase Query in Lucene 4.3. It is working Perfect
> for all scenarios except the below scenario.
> When I try to Search for a phrase which is pre
Hi,
I am Trying to do Multiphrase Query in Lucene 4.3. It is working Perfect
for all scenarios except the below scenario.
When I try to Search for a phrase which is preceded by any punctuation,it
is not working..
TextContent: Dremel is a scalable, interactive ad-hoc query system for
analysis
of
I've never had to do that, but a quick Google search brought this up:
http://stackoverflow.com/questions/9935177/how-to-repair-corrupted-lucene-index
Another (possibly better and definitely safer) solution would be to log
your updates in a way that would allow you to reprocess them in sequence.
It
I'd write a shutdown method that calls close() in a controlled manner
and invoke it at 23:55. You could also call commit() at whatever
interval makes sense to you but if you carried on killing the JVM
you'd still be liable to lose any docs indexed since the last commit.
This is standard stuff jus
Team,
We have our app using lucene 4.1. Docs keep getting indexed and we
close the index by 00.00 hrs every day and open a new one for the next
calendar day, however in case of an abrupt shutdown/kill of the JVM, the
app server crashes and the live indexes end up remaining without a
segme
Then I suggest you start a new thread, posting all relevant details
and preferably a cut down but complete program, with all relevant
code, and no irrelevant code, with simple examples, input and output,
of what does and doesn't work,
--
Ian.
On Thu, Oct 3, 2013 at 12:28 PM, VIGNESH S wrote:
>
Ian,
Thanks for your reply..
I am facing the same problem if i use whiteSpaceTokenizer also.
My analyzer works perfect in case of Lucene 3.6.
Thanks and Regards
Vignesh Srinivasan
On Thu, Oct 3, 2013 at 3:23 PM, Ian Lea wrote:
> Certainly sounds like a bug in your analyzer. You could start a n
Certainly sounds like a bug in your analyzer. You could start a new
thread if you need help with that. But from your previous email it
sounds like you could use WhitespaceTokenizer chained with
LowerCaseFilter.
--
Ian.
On Thu, Oct 3, 2013 at 7:16 AM, VIGNESH S wrote:
> Hi,
>
> In my Analyzer
Hi
You need to expand the field as below. Store the document and its
associated values as one document.
Document Field-A Stored-Field
D1 a1 1,2
D2 a2 3,10
Other alternative approach is to store these fields external to Lucene, may
be in dat
15 matches
Mail list logo