all your hard work!
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: New Feature
>
test patch. All tests (core, contrib, tag) pass and
javadocs look good.
I'll commit this in a day or two!
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
>
486.
I'm still learning JIRA :), I didn't the comment know was going to get posted
in this thread,
I was assuming it was the LUCENE-1486, that was going to get the comment.
> New flexible query parser
> -
>
> Key: LUCENE-1567
>
5 PM:
I created a block dependency on LUCENE-1486.
The "new flexible query parser" blocks LUCENE-1486.
was (Author: lafa):
Depend on the "new flexible query parser" work.
> New flexible query parser
> -
>
> Key: LUCE
-1486, that was going to get the comment.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: N
ble query parser" work.
{quote}
OK, didn't know there was another patch coming I guess I'll redo my
verification then...
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://is
s, let me know if you find any wrong with the new patch.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
>
this is all I changed, but it might have some other minor changes.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
>
ssor
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: New Feature
> Components: QueryParse
at changes are hard to track.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: New Feature
09july28_v10.patch,
> lucene_trunk_FlexQueryParser_2009july30_v12.patch,
> lucene_trunk_FlexQueryParser_2009March24.patch,
> lucene_trunk_FlexQueryParser_2009March26_v3.patch, new_query_parser_src.tar,
> QueryParser_restructure_meetup_june2009_v2.pdf,
> wiki_switching_to_the_new_que
ira issue" with the description of the feature,
so we can discuss the details there.
I'll try to implement that once we agree on all the details.
{quote}
Will do! Thanks.
> New flexible query parser
> -
>
> Key: LUCENE-15
stake. Thanks for
reporting that. Here is the new patch ;)
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
>
your patch v11, the size almost doubled.
I did a diff with v10 and it looks like all the files show up twice on v11
patch.
Can you resubmit it again, I'll add the docs for messages after you resubmit it.
> New flexible query parser
> -
>
>
ood description about it. Luis
has a good knowledge about this package, if you have time, can you add this
file to that package? Thanks :)
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apac
here.
I'll try to implement that once we agree on all the details.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Ja
in top-level places, such as
the package.html of your new package, we should not have TODOs in the docs.
Please fix that soon, 2.9 is coming quickly.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https
s is and so it correctly creates a NumericRangeQuery for
strings like "[1.567..*]" or "(1.787..19.5]". NumericRangeQuery also supports
the rewrite modes, only some type of schema support is missing.
I ask this, because someone asked on java-user for such a feature in query
pa
atch tomorrow with these changes.
{quote}
Sounds good. Could you also please fix the javadocs? When I'm building the
javadocs I'm getting a lot of warnings about not found references.
Otherwise I think this is ready to commit soon.
> New flex
it a new version of the patch anyway? If yes, can you make
this change?
If no I can submit a new patch...
{quote}
Sorry Michael, by one minute, I did not see your comment. I will submit another
patch tomorrow with these changes.
> New flexible query
fixed every javadocs referencing *QueryParserWrapper
- Fixed javadoc warnings
- Fixed javadocs (text)
- Added getAnalyzer() to LuceneQueryParserHandler
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.
ake
this change?
If no I can submit a new patch...
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
>
mmon-build.xml has support for this, maybe it is
just using an already available target/macro.
{quote}
Thanks, I'll take a look and see if I can reuse it.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issue
et to the queryparser build file, in the near
future to make that easier
The main Lucene build.xml/common-build.xml has support for this, maybe it is
just using an already available target/macro.
> New flexible query parser
> -
>
>
eryparser build file, in the near
future to make that easier
{quote}
I would love that!
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Luc
amed LuceneQueryConfigHandler.setConstantScoreRewrite to
setMultiTermRewriteMethod. Shouldn't ConstantScoreRewriteAttribute class (and
its impl) be renamed too?
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: h
s.
Not a big deal, but we should always use the generated code from javacc,
and avoid editing those generated files, this will avoid inconsistencies.
I'll try to add a javacc target to the queryparser build file, in the near
future to make that easier :)
> New flex
the generated code from javacc,
and avoid editing those generated files, this will avoid inconsistencies.
I'll try to add a javacc target to the queryparser build file, in the near
future to make that easier :)
> New flexible query parser
> -
>
>
earer and less confusing.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: New Feature
>
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luis Alves updated LUCENE-1567:
---
Attachment: (was: lucene_trunk_FlexQueryParser_2009july27_v9.patch)
> New flexible query par
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luis Alves updated LUCENE-1567:
---
Attachment: lucene_trunk_FlexQueryParser_2009july27_v9.patch
> New flexible query par
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luis Alves updated LUCENE-1567:
---
Attachment: lucene_trunk_FlexQueryParser_2009july27_v9.patch
> New flexible query par
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luis Alves updated LUCENE-1567:
---
Attachment: (was: lucene_trunk_FlexQueryParser_2009july27_v9.patch)
> New flexible query par
el changes.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Quer
rant?
Yes.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Query
h to work with the latest code in svn.
I like your suggestion about creating a core package,
I'll re-factor the code to use the core package.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apach
sing now that the different main folders,
such as builders, processors, etc. share the same root with 'original', which
is an actual implementation.
Could we change the packaging here? Maybe we could create
contrib/queryparser/core and move builders, processors, etc. there?
> New flex
e it could use some more
documentation...
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: N
:
- Attributes needed to be changed after LUCENE-1693 was committed
- Needed to change constantScoreRewrite to RewriteMethod (LUCENE-1644)
I also added back the build.xml and pom.xml.template from the v7 patch.
All tests pass now again.
> New flexible query par
set to UTF-8 in my eclipse project when I
applied the patch.
I changed it to UTF-8, reapplied, and now it works fine.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira
xpected:<[?]> but was:<[?]>
[junit] at
org.apache.lucene.messages.TestNLS.testNLSLoading_ja(TestNLS.java:54)
[junit] Test org.apache.lucene.messages.TestNLS FAILED
{noformat}
> New flexible query parser
> -
>
>
t me know what is the best option for you.
Sorry for the mistake
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
>
the latest patch.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: New Feature
>
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch reassigned LUCENE-1567:
-
Assignee: Michael Busch (was: Grant Ingersoll)
> New flexible query par
fusion with
the old query parser, which is also called QueryParser
- fixed the identation (I hope), the patch now contains 2-space identation
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.o
you know an easy and automated way to do that? It will
take forever to do manually.
{quote}
Just change your eclipse settings (Java Code Style -> Formatter) to 2-space
indentation (only whitespaces) and then do Source -> Correct Indentation.
No reason to be scared! :)
> New fle
he new.
{quote}
Sure, I will work on that and add some javadocs pointing to the new classes.
{quote}
Also, can you fix all indentation to 2-space in the next patch iteration?
{quote}
Wow, I'm scaried now, do you know an easy and automated way to do that? It will
take forever to do manu
ance to Incubator. It now has 3 days to
percolate under a lazy consensus review. After that, assuming it passes, this
can be committed.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org
But that's a nice-to-have for 2.9.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: New Feature
&
e
don't we need to make corresponding subclasses of the new queryParser for these?
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project
will help users to switch over to the new query
parser. I think it's pretty simple and helpful.
Just take a look, I will appreciate any suggestion.
I plan to add it to Lucene wiki after the query parser code is committed.
> New flexible quer
the version number/platform of the tool used to create
it.
{quote}
md5sum version is included in coreutils 6.10-6ubuntu1 The GNU core utilities
OS: Ubuntu Jaunty 2.6.28-13-server i686 GNU/Linux
> New flexible query parser
> -
>
>
ning item on my list. Then I can submit the
IP-Clearance to incubator for lazy consensus vote and then this can be
committed.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira
ve also noticed that when building using "ant build-contrib" it does not
copy .properties files to the jar. The new query parser uses a property file to
read the NLS messages from and I'm getting some message warnings when running
the tests. Is anybody getting the sam
;original" and my +1 for "original"
{quote}
+1 for "original"
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Proje
undo my changes on the build files to skip the
queryparser module if jdk 1.4 was found
{quote}
Cool!
{quote}
I'll add 2 more suggestions
"standard", "standardSyntax". I will give +1 for "standard".
{quote}
I would like to suggest also "original" and
I'll add 2 more suggestions
"standard", "standardSyntax". I will give +1 for "standard".
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCE
to skip queryparser module if jdk 1.4 was
found.
- Include Adriano changes
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
>
ot;defaultLucene", "default" or "main". I will give +1 for
"default".
Regards,
Adriano Crestani Campos
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.ap
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1567:
---
Fix Version/s: 2.9
> New flexible query par
ting 1.5 code in 3.0 we may make certain changes (switch to
generics in certain APIs; move the new QueryParser into core; etc.).
{quote}
OK sounds like a plan then! The new QP code will not change, but we'll move it
into core in 3.0.
> New flexible
ring an email or two from Mike that
mentioned differently (waiting till 3.1) ... but I just found one of the
threads discussing it and it looks like consensus shifted:
http://www.lucidimagination.com/search/document/6d2b6488b4115/2_9_3_0_plan_java_1_5#6d2b6488b4115
> New flexible query
However we don't plan on doing any new features, etc in 3.0; that will
first happen in 3.1.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
>
http://wiki.apache.org/lucene-java/Java_1.5_Migration
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: New Feat
but Mike has indicated that 3.0 would just be a quick bug fix release with
deprecations removed from 2.9. I thought I'd seen him say that 3.1 would
actually be the first with 1.5?
Mike M?
> New flexible query parser
> -
>
> Key: LUCENE-15
or some other number on the end are pretty much
meaningless. I'd suggest finding something better that actually describes what
the package contains. After all what is the "second" query parser?
> New flexible query parser
> -
>
>
yParser.lucene3 <- lucene 3.X syntax
org.apache.lucene.queryParser.xml <- some XML syntax
org.apache.lucene.queryParser.luceneBoolean <- boolean syntax
org.apache.lucene.queryParser.explicit <- explict query language syntax
I'll also help on the when wiki the code is
extra jar in their classpath.
Looking at the latest patch, that's what it does (new one to contrib while
deprecating old one).
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apach
thing though?
We should get things fully straightened out before you spend too much time
switching between 1.4 and 1.5 though.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/L
sed on his response there is no
need for contrib projects to be able to compile using JDK 1.4. So, Luis, could
you rollback your changes you did on the build files?
Thanks,
Adriano Crestani Campos
> New flexible query parser
> -
>
> Key: LU
quot;ant build-contrib" using Java 1.4, it fails, I even
tried a clean trunk and it did not work. Were you able to run it using 1.4 Luis?
I already opened a thread on the ML about this:
http://markmail.org/thread/3fyldf7t423fhwbm
> New flexible query parser
>
not even committed, agreed?
Suggestions?
Regards,
Adriano Crestani Campos
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucen
d15.xml when a jdk15 is present.
I tested default, build-contrib, javadocs-contrib all work fine.
I just uploaded the patch v5 with this fix.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.
ne_trunk_FlexQueryParser_2009March26_v3.patch, new_query_parser_src.tar,
> QueryParser_restructure_meetup_june2009_v2.pdf
>
>
> From "New flexible query parser" thread by Micheal Busch
> in my team at IBM we have used a different query parser than Lucene's in
> our p
he package.html of the new contrib package
that will help users who want to use the queryparser to get started.
{quote}
I was also thinking about a wiki page that would guide Lucene users to migrate
to the new query parser using this new interface.
More suggest
the user runs JRE 1.4, but it should rather
skip the new query parser contrib. You can use this property, which is definied
in common-build.xml:
{code}
{code}
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: h
10th of July.
--
Cheers,
David
Nuix Pty Ltd
Suite 79, 89 Jones St, Ultimo NSW 2007, AustraliaPh: +61 2 9280 0699
Web: http://www.nuix.comFax: +61 2 9212 6902
> New flexible query parser
> -
>
>
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: New Feature
> Components: QueryParser
&g
he lucene
builders?
And please add a simple junit that demonstrates the usage of that interface and
ideally some documentation into the package.html of the new contrib package
that will help users who want to use the queryparser to get started.
> New flexible
rk a formality. At any rate, as I said, the discussion of Trie,
LocalLucene and when some generic piece of code needs a grant has nothing to do
with this particular issue, so please, if you want to continue this
conversation, then start one on java-dev.
> New flexible query
Mark Miller (JIRA) wrote:
Mark Miller commented on LUCENE-1567:
-
I'll just keep my response out of JIRA to avoid taking over that issue:
Nevermind. Sorry. JIRA is too smart for me ;)
--
- Mark
eeds the grant.
- Mark
--
- Mark
http://www.lucidimagination.com
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
&g
onate
it. And now I am committer and already signed the CLA. If there is still a
problem, I would open another issue about that.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org
t an accusation, but an attempt to
clarify what requires this and what doesn't. As a committer, its important that
this information is clear to me. As the PMC head, I'd think youd be more
helpful with the matter.
> New flexible query parser
> -
>
>
Trie. Anyway, this issue is not the place for
this discussion.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
>
the law in Intellectual Property
Clearance, then LocalLucene and Trie and a lot of other stuff also needed this
clearance ... I may have just missed the process on those though.
> New flexible query parser
> -
>
> Key: LUCENE-1567
>
subject than I do.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: New Feature
> Compone
ther Apache project
Just because someone else does it wrong... It's pretty clear in this case that
the Grant is necessary.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org
edge
about it. But if someone wanted to research further ...
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
>
they exist and align w/ the Grant. What we commit can be
patched.
{quote}
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
>
that asap. Thanks for explaining, Grant.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: New
Parser
> Environment: N/A
>Reporter: Luis Alves
>Assignee: Grant Ingersoll
> Attachments: lucene_trunk_FlexQueryParser_2009March24.patch,
> lucene_trunk_FlexQueryParser_2009March26_v3.patch,
> QueryParser_restructure_meetup_june2009_v2.pdf
>
>
&
[
https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720404#action_12720404
]
Michael Busch commented on LUCENE-1567:
---
Ok GO!
> New flexible query
one week at max!
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
> Issue Type: New Feature
>
code before we can commit. From which patch do
you need the MD5/SHA1 hash from?
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
for clearance are:
1. tarball and hash
2. Vote on Incubator for clearance.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Java
>
onsider yourself reminded:
{quote}
Remind active committers that they are responsible for
ensuring that a Corporate CLA is recorded if such is
required to authorize their contributions under their
individual CLA.
{quote}
> New flexible qu
lude the version number of
the software used to create the hash.
See https://issues.apache.org/jira/browse/INCUBATOR-77 for example.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira
http://incubator.apache.org/ip-clearance/ip-clearance-template.html) for the
exact code listed in the software grant. Also include the version number of
the software used to create the hash.
See https://issues.apache.org/jira/browse/INCUBATOR-77 for example.
> New flexible query
;d like to get this in 2.9 because it seems to be a popular
issue.
> New flexible query parser
> -
>
> Key: LUCENE-1567
> URL: https://issues.apache.org/jira/browse/LUCENE-1567
> Project: Lucene - Ja
1 - 100 of 153 matches
Mail list logo
