I'd like to engage someone to develop a stand-alone GUI for a Lucene
database. I'm thinking something on the order of Luke but simpler and
more tailored to the database itself. It is a database of US patents
since 1976.
If you know of someone who might be interested would you kindly have
them get
xpressions.
>
> To have highlighting and validation in an editor would be great!
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
>
> *From: *Scott Guthery
> *Sent: *11 November 2020 23:54
> *To: *[email protected]
>>> I wish something like this existed for streaming expressions.
I'm not sure what you mean by 'streaming expressions' but yacc/bison and
lex/flex can be applied to bytes coming from any stream and hitch syntax
and semantic actions onto anything they recognize. There is, naturally,
the proviso t
I wish something like this existed for streaming expressions.
To have highlighting and validation in an editor would be great!
Sent from Mail for Windows 10
From: Scott Guthery
Sent: 11 November 2020 23:54
To: [email protected]
Subject: Re: Lucene Query Parser Syntax Specification
>&g
There is no single query parser that covers all of Lucene's API
(various Query class implementations). The existing "query parsers"
cover subsets of the API - historically they vary depending on what
people needed, what kind of audience was targeted (technical users,
general public)...Many factors.
>> The source code is the de-facto specification
Fair enough although it does beg the question of which parser source code,
there being no shortage of Lucene/Solr/etc. query parsers, parser releases,
and parser versions at github. Anyway, below is my de jure yacc. I think
it covers everything in
> 1) Has this already been done?
There are a number of query parsers in Lucene. Some of them are
implemented as javacc grammars - these should be convertible to
yacc/lex (do you really need C implementations though?).
> 2) Is there a newer version of the specification?
The source code is the de-
I'm building a yacc/lex pair for the Apache Lucene Query Parser Syntax.
1) Has this already been done?
I'm using the specification published on 4/11/2012.
2) Is there a newer version of the specification?
I'm hitting shift/reduce conflicts and some constructs that I think should
be accepted by on