> Yes, it won't be a really atomic switch
While it may not be completely atomic, could it be closer? GitHub already
supports new issues, developers are just advised against opening there.
Could the order of events be:
1. Make Jira read only
2. Send a message to dev@ stating new issues should now
This is great work Tomoko! A couple minor thoughts:
* I don’t think a flood of notifications from the import is a problem. It’s
a one time hassle, and having the actual user links is nice for GitHub’s
cross linking system.
* Do you have an estimate for how many api calls are needed? How many tota
+1
On Mon, May 30, 2022 at 08:40 Tomoko Uchida
wrote:
> Hi everyone!
>
> As we had previous discussion thread [1], I propose migration to GitHub
> issue from Jira.
> It'd be technically possible (see [2] for details) and I think it'd be
> good for the project - not only for welcoming new develop
> perhaps we could borrow a solution from other large/popular projects
operated on GitHub (yes, Elasticsearch and OpenSearch are in my mind).
FWIW Elasticsearch uses a separate, issue only, private repo with limited
developer access for security issues. I have no idea how feasible that
would be fo
Good luck on getting rid of those squirrels, Erick. Maybe this will give
you inspiration for other ways to get rid of them. It was one of the
coolest talks I can remember attending.
https://www.youtube.com/watch?v=QPgqfnKG_T4
On Wed, Dec 30, 2020 at 6:09 AM Erick Erickson
wrote:
> 40 years is e
and all who
voted!
On Tue, Sep 1, 2020 at 1:21 PM Ryan Ernst wrote:
> Dear Lucene and Solr developers!
>
> Sorry for the multiple threads. This should be the last one.
>
> In February a contest was started to design a new logo for Lucene
> [jira-issue]. The initial attempt [fir
I forgot to vote myself. :)
(binding)
A1, A2, D
On Tue, Sep 1, 2020 at 1:21 PM Ryan Ernst wrote:
> Dear Lucene and Solr developers!
>
> Sorry for the multiple threads. This should be the last one.
>
> In February a contest was started to design a new logo for Lucene
> [jira-i
Enforcing version and gradlew vs local shouldn't be difficult. As you said,
Uwe, the version is gettable programmatically, and could be checked in the
same check-environment script Dawid already mentioned. Whether or not the
gradle wrapper is being used is a little tricker, but the code source for
The only difference between running your local /usr/bin/gradle vs gradlew
should potentially be the gradle version. The purpose of gradlew is to
allow a project to force a particular version of gradle. Maintaining
backcompat in build.gradle files for features gradle has changed or removed
is diffic
Each variant is counted separately. This is why we are doing rank choice
voting. So if you are ok with either A2 or A1, specify both in your vote.
See the rules section in my original email.
On Tue, Sep 1, 2020, 23:00 Shawn Heisey wrote:
> On 9/1/2020 2:21 PM, Ryan Ernst wrote:
> > In
Dear Lucene and Solr developers!
Sorry for the multiple threads. This should be the last one.
In February a contest was started to design a new logo for Lucene
[jira-issue]. The initial attempt [first-vote] to call a vote resulted in
some confusion on the rules, as well the request for one additi
dev@ got dropped from this, including the note here as well
On Tue, Sep 1, 2020 at 12:15 PM Ryan Ernst wrote:
> Apologies Baris, I messed up the links because I copied the first of
> your links, and then replaced the number, thinking that would work
> correctly. But..computers.
>
Dear Lucene and Solr developers!
In February a contest was started to design a new logo for Lucene
[jira-issue]. The initial attempt [first-vote] to call a vote resulted in
some confusion on the rules, as well the request for one additional
submission. I would like to call a new vote, now with mor
retains the same idea as our current logo with a
>> more modern look.
>>
>> On Wed, Jun 17, 2020 at 4:58 PM Andi Vajda wrote:
>>
>>>
>>> C. (current logo)
>>>
>>> Andi.. (pmc)
>>>
>>> On Jun 15, 2020, at 15:08, Ryan
Dear Lucene and Solr developers!
In February a contest was started to design a new logo for Lucene [1]. That
contest concluded, and I am now (admittedly a little late!) calling a vote.
The entries are labeled as follows:
A. Submitted by Dustin Haver [2]
B. Submitted by Stamatis Zampetakis [3] N
+1 (binding)
On Tue, May 12, 2020 at 12:37 AM Dawid Weiss wrote:
> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development
The Lucene PMC would like to have a contest to replace the Lucene logo. You
can find details at:
https://issues.apache.org/jira/browse/LUCENE-9221
Hi Ryan,
>
> Do you have a wip patch? That will be helpful for others who want to
> continue from your work. The current ant build have tons of tasks but we
> may want to port several most important tasks.
>
>
> On Thu, Oct 11, 2018 at 8:37 PM Ryan Ernst wrote:
>
>>
There was an issue before (https://issues.apache.org/jira/browse/LUCENE-5755)
that looked at switching to some other build system. A few were discussed,
but at the time nobody had the time to do the work. I've investigated
migrating to gradle a couple times in the past, but there is so much stuff
i
This is how Elasticsearch encodes binary values. The first value a vint
containing the number of values for the field. In Lucene, binary doc values
do not have a concept of "multi valued"; the data is opaque.
On Wed, Feb 28, 2018 at 8:25 AM Dominik Safaric
wrote:
> No I'm not. The values are bei
After changing that constant check, do you get the same test failures? What
are the actual failure messages?
On Mon, Jun 26, 2017 at 10:38 AM Anshum Gupta
wrote:
> Thanks Adrien, sadly, the tests aren't passing. That's the reason why I
> didn't push the changes. I'll see if someone else can help
Junit 5 hasn't been released yet, they are on milestone 4. We did add some
junit 5 behavior to LuceneTestCase last year though:
https://issues.apache.org/jira/browse/LUCENE-7009
On Thu, Jun 15, 2017 at 2:45 PM Erick Erickson
wrote:
> I may regret this, but is there any interest in moving to Juni
[
https://issues.apache.org/jira/browse/LUCENE-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563393#comment-15563393
]
Ryan Ernst commented on LUCENE-7485:
Looks good! A couple minor suggestions:
[
https://issues.apache.org/jira/browse/LUCENE-7453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15511049#comment-15511049
]
Ryan Ernst commented on LUCENE-7453:
bq. this is probably a multicrit
[
https://issues.apache.org/jira/browse/LUCENE-7453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15511042#comment-15511042
]
Ryan Ernst commented on LUCENE-7453:
bq. I don't like overloading index
[
https://issues.apache.org/jira/browse/LUCENE-7453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510784#comment-15510784
]
Ryan Ernst commented on LUCENE-7453:
bq. although I do dislike using suc
[
https://issues.apache.org/jira/browse/LUCENE-7453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510719#comment-15510719
]
Ryan Ernst commented on LUCENE-7453:
I'm ok with {{docIndex}}, it is at
Ryan Ernst created LUCENE-7453:
--
Summary: Change naming of variables/apis from docid to docnum
Key: LUCENE-7453
URL: https://issues.apache.org/jira/browse/LUCENE-7453
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-7314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318482#comment-15318482
]
Ryan Ernst commented on LUCENE-7314:
Another reason to have good defaults in cor
[
https://issues.apache.org/jira/browse/LUCENE-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254411#comment-15254411
]
Ryan Ernst commented on LUCENE-7249:
Real polygons are starting to move
[
https://issues.apache.org/jira/browse/LUCENE-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254109#comment-15254109
]
Ryan Ernst commented on LUCENE-7242:
Glad the idea worked out! +1
> Lat
[
https://issues.apache.org/jira/browse/LUCENE-7239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252697#comment-15252697
]
Ryan Ernst commented on LUCENE-7239:
+1, nice speed up!!
> Speed up LatLon
[
https://issues.apache.org/jira/browse/LUCENE-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246445#comment-15246445
]
Ryan Ernst commented on LUCENE-7229:
+1 to the new patch, thanks for the impr
[
https://issues.apache.org/jira/browse/LUCENE-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246430#comment-15246430
]
Ryan Ernst commented on LUCENE-7229:
+1 to the patch.
One suggestion on readabi
[
https://issues.apache.org/jira/browse/LUCENE-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238093#comment-15238093
]
Ryan Ernst commented on LUCENE-7202:
bq. If I want to support Hilbert or Moor
[
https://issues.apache.org/jira/browse/LUCENE-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235946#comment-15235946
]
Ryan Ernst commented on LUCENE-7155:
+1 to the latest patch.
> Script addVer
[
https://issues.apache.org/jira/browse/LUCENE-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235688#comment-15235688
]
Ryan Ernst commented on LUCENE-5325:
[~romseygeek] sounds like an interesting
[
https://issues.apache.org/jira/browse/LUCENE-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224331#comment-15224331
]
Ryan Ernst commented on LUCENE-7155:
Ah this is a bug! We don't do major
Welcome!
On Mon, Apr 4, 2016 at 7:40 AM, Karl Wright wrote:
> Hi all,
>
> Professionally, I've been active in software development since the
> 1970's. My interests include many things related to software development,
> as well as areas as varied as geology, carpentry, and gardening. I'm the
>
[
https://issues.apache.org/jira/browse/LUCENE-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222350#comment-15222350
]
Ryan Ernst commented on LUCENE-7155:
[~janhoy] The branch type major is used
[
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219107#comment-15219107
]
Ryan Ernst commented on LUCENE-6938:
It looks like the branch detection logic i
[
https://issues.apache.org/jira/browse/LUCENE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218211#comment-15218211
]
Ryan Ernst edited comment on LUCENE-7150 at 3/30/16 4:0
[
https://issues.apache.org/jira/browse/LUCENE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218211#comment-15218211
]
Ryan Ernst edited comment on LUCENE-7150 at 3/30/16 4:0
[
https://issues.apache.org/jira/browse/LUCENE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218211#comment-15218211
]
Ryan Ernst commented on LUCENE-7150:
Thanks for the patch [~daddywri]! I'm
[
https://issues.apache.org/jira/browse/LUCENE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216947#comment-15216947
]
Ryan Ernst commented on LUCENE-7150:
bq. It escapes me why degrees and distanc
[
https://issues.apache.org/jira/browse/LUCENE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216918#comment-15216918
]
Ryan Ernst commented on LUCENE-7150:
bq. One problem at the moment is that al
[
https://issues.apache.org/jira/browse/LUCENE-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst resolved LUCENE-7147.
Resolution: Fixed
Assignee: Ryan Ernst
Fix Version/s: 6.1
master
[
https://issues.apache.org/jira/browse/LUCENE-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216218#comment-15216218
]
Ryan Ernst edited comment on LUCENE-7147 at 3/29/16 6:0
[
https://issues.apache.org/jira/browse/LUCENE-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst updated LUCENE-7147:
---
Attachment: (was: example-crosses-axis-not-center.html)
> Improve disjoint check for
[
https://issues.apache.org/jira/browse/LUCENE-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst updated LUCENE-7147:
---
Attachment: example-crosses-axis-not-center.html
> Improve disjoint check for geo distance qu
[
https://issues.apache.org/jira/browse/LUCENE-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst updated LUCENE-7147:
---
Attachment: example-intersects-bbox-not-circle.html
example-crosses-axis-not
[
https://issues.apache.org/jira/browse/LUCENE-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215513#comment-15215513
]
Ryan Ernst edited comment on LUCENE-7147 at 3/29/16 6:1
[
https://issues.apache.org/jira/browse/LUCENE-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215513#comment-15215513
]
Ryan Ernst edited comment on LUCENE-7147 at 3/29/16 6:1
[
https://issues.apache.org/jira/browse/LUCENE-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst updated LUCENE-7147:
---
Attachment: LUCENE-7147.patch
Here is a patch which adds the following simple logic: if the rect of
Ryan Ernst created LUCENE-7147:
--
Summary: Improve disjoint check for geo distance query traversal
Key: LUCENE-7147
URL: https://issues.apache.org/jira/browse/LUCENE-7147
Project: Lucene - Core
On Fri, Mar 25, 2016 at 10:17 AM, Chris Hostetter
wrote:
> Ultimately that seems like history that should *not* be on the master
> branch .. preserved, sure -- great even that it's in git and easily
> browsable/comparable (unlike reivewing the evolution of patch files
> attached to jira) but i do
On Fri, Mar 25, 2016 at 9:59 AM, Chris Hostetter
wrote:
> It may only create a single commit, but from the perspective of people
> viewing master, it "adds" every commit that was on the jira/SOLR-445
> branch to the master branch -- generating an metric ass-ton of
> emails among other things, but
Scalar doesnt mean anything. Point is simple, it is a point in n
dimensional space, that is what the data structure provides for fast
searching on. Numbers are points in one dimensional space. Think of a
number line.
On Mar 24, 2016 8:37 AM, "David Smiley" wrote:
> bq. it wasn't at all clear that
[
https://issues.apache.org/jira/browse/LUCENE-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203500#comment-15203500
]
Ryan Ernst commented on LUCENE-7118:
Shouldn't this line in PointRangeQuery
[
https://issues.apache.org/jira/browse/LUCENE-7077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184296#comment-15184296
]
Ryan Ernst commented on LUCENE-7077:
+1
> fail precommit on useless ass
This sounds good, but isn't the repo name redundant given it is implied by
the email going to commits@l.a.o?
On Feb 19, 2016 4:38 PM, "Chris Hostetter" wrote:
>
> : https://git-wip-us.apache.org/docs/switching-to-git.html seems to
> : suggest there is per project flexibility. Branch not one of th
[
https://issues.apache.org/jira/browse/LUCENE-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15145113#comment-15145113
]
Ryan Ernst commented on LUCENE-7023:
The spec for manifest files has a limit o
> Are you sure *all* back porting will be done by cherry picking?
Using merge commits for backporting would require resolving all differences
between master and the stable branch. From what I've seen, using merge
commits between two long lived branches usually happens in other projects
by forward
> unless i'm missing something, only getting email/jira
> notifications the first time a specific commit was seen would mean that
> when backporting from master to 5x (or 6x down the road) there would be no
> tracking email/comment ... which would make it much harder to know when
> things were back
nches we care about. Creating noise for everyone's random work branches
>>>> is crazy.
>>>>
>>>> - Mark
>>>>
>>>> On Wed, Feb 3, 2016 at 3:09 PM david.w.smi...@gmail.com <
>>>> david.w.smi...@gmail.com> wrote:
>>
FYI, I just renamed the "Trunk" version to "master", to match what we have
now with git. Since it was just a rename, it appears all the existing
issues that used Trunk as a fix version are already updated.
[
https://issues.apache.org/jira/browse/LUCENE-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst resolved LUCENE-7009.
Resolution: Fixed
Assignee: Ryan Ernst
Fix Version/s: Trunk
> Add expectThr
[
https://issues.apache.org/jira/browse/LUCENE-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst updated LUCENE-7009:
---
Attachment: LUCENE-7009.patch
Patch.
> Add expectThrows utility to LuceneTestC
Ryan Ernst created LUCENE-7009:
--
Summary: Add expectThrows utility to LuceneTestCase
Key: LUCENE-7009
URL: https://issues.apache.org/jira/browse/LUCENE-7009
Project: Lucene - Core
Issue Type
By the way, I meant I attended a talk *about git at apache*
On Feb 2, 2016 19:50, "Ryan Ernst" wrote:
> This is expected, as merging in the commit to a branch does create a new
> commit for that branch (or rather it is then visible in the history of that
> branch whil
This is expected, as merging in the commit to a branch does create a new
commit for that branch (or rather it is then visible in the history of that
branch while before it was not).
Two years ago at ApacheCon I attended a talk by David Nalley. This issue
was brought up, and I spoke a little with h
I agree merges are better to use than rebasing. Rebasing just makes
development more complicated, and if you want to squash, you can always do
so with merge --squash (as Dawid pointed out on this thread). Especially
having a rule that everyone *must* rebase doesn't seem right.
On Tue, Jan 19, 2016
[
https://issues.apache.org/jira/browse/LUCENE-6982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105695#comment-15105695
]
Ryan Ernst commented on LUCENE-6982:
+1
> throw IAE on illegal bm25 pa
While this isn't something we have tests for in TestBackwardsCompatibility
(that only tests every previous version against the current version), we do
have tests in TestVersion for parsing versions that do not have constants
(see testForwardsCompatibility). Version constants are only shortcuts to
V
[
https://issues.apache.org/jira/browse/LUCENE-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088236#comment-15088236
]
Ryan Ernst commented on LUCENE-6965:
+1 to Uwe's suggestion. I did not know
[
https://issues.apache.org/jira/browse/LUCENE-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088092#comment-15088092
]
Ryan Ernst commented on LUCENE-6965:
Thanks...looks ok I guess then.
> Expre
[
https://issues.apache.org/jira/browse/LUCENE-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088078#comment-15088078
]
Ryan Ernst commented on LUCENE-6964:
+1
> Small changes in expressions
[
https://issues.apache.org/jira/browse/LUCENE-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15087966#comment-15087966
]
Ryan Ernst commented on LUCENE-6965:
ParseException seems fine, but why
[
https://issues.apache.org/jira/browse/LUCENE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042367#comment-15042367
]
Ryan Ernst commented on LUCENE-6919:
+1 to the idea
> Change the Scorer
[
https://issues.apache.org/jira/browse/LUCENE-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041379#comment-15041379
]
Ryan Ernst commented on LUCENE-6918:
+1, looks good.
For the changes entry, I t
[
https://issues.apache.org/jira/browse/SOLR-8363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037627#comment-15037627
]
Ryan Ernst commented on SOLR-8363:
--
See {{update_example_solrconfigs}} in {{dev-t
[
https://issues.apache.org/jira/browse/LUCENE-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945626#comment-14945626
]
Ryan Ernst commented on LUCENE-6825:
This looks good. I think this is a great
[
https://issues.apache.org/jira/browse/LUCENE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909843#comment-14909843
]
Ryan Ernst commented on LUCENE-6305:
+1 to enabling all the
[
https://issues.apache.org/jira/browse/LUCENE-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735508#comment-14735508
]
Ryan Ernst commented on LUCENE-6773:
Test looks good, thanks!
> Always
[
https://issues.apache.org/jira/browse/LUCENE-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734291#comment-14734291
]
Ryan Ernst commented on LUCENE-6773:
+1
Can you add a test to TestConjunction
[
https://issues.apache.org/jira/browse/LUCENE-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698473#comment-14698473
]
Ryan Ernst commented on LUCENE-6739:
Requiring 1.8 actually makes it *harder*
[
https://issues.apache.org/jira/browse/LUCENE-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698472#comment-14698472
]
Ryan Ernst commented on LUCENE-6739:
> people using MacOSX would have p
[
https://issues.apache.org/jira/browse/LUCENE-6729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679659#comment-14679659
]
Ryan Ernst commented on LUCENE-6729:
+1
> Upgrade ASM version to 5.0.4 (expr
Congrats!
On Tue, Jul 21, 2015 at 12:21 AM, Adrien Grand wrote:
> I'm pleased to announce that Mikhail Khludnev has accepted the PMC's
> invitation to become a committer.
>
> Mikhail, it's tradition that you introduce yourself with a brief bio.
>
> Your handle "mkhl" has already added to the “lu
[
https://issues.apache.org/jira/browse/LUCENE-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612804#comment-14612804
]
Ryan Ernst commented on LUCENE-6655:
This is intentional. All of the anal
[
https://issues.apache.org/jira/browse/LUCENE-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst updated LUCENE-6630:
---
Attachment: LUCENE-6630.patch
Patch.
> Further improve memory of FieldIn
Ryan Ernst created LUCENE-6630:
--
Summary: Further improve memory of FieldInfos
Key: LUCENE-6630
URL: https://issues.apache.org/jira/browse/LUCENE-6630
Project: Lucene - Core
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst resolved LUCENE-6585.
Resolution: Fixed
> Make ConjunctionDISI flatten sub ConjunctionDISI instan
[
https://issues.apache.org/jira/browse/LUCENE-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst updated LUCENE-6585:
---
Fix Version/s: Trunk
5.3
> Make ConjunctionDISI flatten sub ConjunctionD
[
https://issues.apache.org/jira/browse/LUCENE-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14600601#comment-14600601
]
Ryan Ernst edited comment on LUCENE-6585 at 6/25/15 3:1
[
https://issues.apache.org/jira/browse/LUCENE-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst updated LUCENE-6585:
---
Attachment: LUCENE-6585.patch
Here's a new patch with {{instanceof}} replaced with {{==}}. I
[
https://issues.apache.org/jira/browse/LUCENE-6591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593603#comment-14593603
]
Ryan Ernst commented on LUCENE-6591:
+1
> Never write negative
[
https://issues.apache.org/jira/browse/LUCENE-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst updated LUCENE-6585:
---
Attachment: LUCENE-6585.patch
Here is a patch collapsing all subconjunctions (thanks [~jpountz] for
[
https://issues.apache.org/jira/browse/LUCENE-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592827#comment-14592827
]
Ryan Ernst commented on LUCENE-6584:
StandardTokenizerFactory now handles versio
[
https://issues.apache.org/jira/browse/LUCENE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579288#comment-14579288
]
Ryan Ernst commented on LUCENE-5954:
+1 to the new patch.
I think the in
1 - 100 of 674 matches
Mail list logo
