Should SOLR-8396 be a prerequisite?
On 25 Jan 2017 10:38, "Christine Poerschke (BLOOMBERG/ LONDON)" <
cpoersc...@bloomberg.net> wrote:
> +1 for May.
>
> I'd like to see https://issues.apache.org/jira/browse/SOLR-8668 in the
> 7.0 release (and have tagged/updated the ticket to indicate so).
>
>
Congratulations Mikhail!
On 30 Dec 2016 15:16, "Adrien Grand" wrote:
> I am pleased to announce that Mikhail Khludnev has accepted the PMC's
> invitation to join.
>
> Welcome Mikhail!
>
> Adrien
>
Welcome Jim!
On 1 Jan 2017 10:05, "Michael McCandless" wrote:
> I'm pleased to announce that Jim Ferenczi has accepted the Lucene
> PMC's invitation to become a committer.
>
> Jim, it's tradition that you introduce yourself with a brief bio.
>
> Your handle "jimczi"
Congratulations Christine!
On 30 Dec 2016 12:47, "Adrien Grand" wrote:
> I am pleased to announce that Christine Poerschke has accepted the PMC's
> invitation to join.
>
> Welcome Christine!
>
> Adrien
>
Welcome Ishan :)
On Tue, Nov 29, 2016 at 6:17 PM, Mark Miller wrote:
> I'm pleased to announce that Ishan Chattopadhyaya has accepted the PMC's
> invitation to become a committer.
>
> Ishan, it's tradition that you introduce yourself with a brief bio /
> origin story,
ionally
>> displays the branch you are on in your shell prompt:
>> https://gist.github.com/yonik/04b2e759eecf5ef96383
>>
>> Example:
>>
>> /opt/code$ cd lusolr
>> [master] /opt/code/lusolr$
>>
>> -Yonik
>>
>>
>> On Sat, Jan 23,
https://git-scm.com/docs/git-credential-cache
Should help with the constant password typing..
On 23 Jan 2016 09:13, "Dawid Weiss" wrote:
> Ok, folks. Seems like code migration is complete, with both gh mirrors
> and Apache repos up.
>
> 1. Please read the docs at:
You're welcome! :)
On 23 Jan 2016 09:31, "Dawid Weiss" <dawid.we...@gmail.com> wrote:
> Thanks Ramkumar. Also thank you for saving that list of PRs, that was
> very thoughtful of you.
>
> Dawid
>
> On Sat, Jan 23, 2016 at 10:26 AM, Ramkumar R. Aiyengar
> <a
Not a big deal, but guys, do check if your mail is set properly in
~/.gitconfig, otherwise commits would show your personal mail as the
author. Committer still shows up as your apache mail address, but many UIs
hide it by default, and might not be apparent to those new to the
project/git..
More to Mark's point, the focus of this effort is to move the repo and not
the development model. Sure, we can debate a lot more on whether rebase or
merge is preferred, bit given that the amount of git experience varies
across committers, it would help to start off as close to SVN as possible,
+1. There might be ways to enforce it on the remote side..
http://stackoverflow.com/questions/2039773/have-remote-git-repository-refuse-merge-commits-on-push
But I am not a git expert enough to tell you exactly what the solution
there is trying to do..
On 19 Jan 2016 19:00, "Mark Miller"
+1
SUCCESS! [0:56:50.593184]
On Mon, Jan 18, 2016 at 7:19 PM, Erick Erickson
wrote:
> +1
>
> SUCCESS! [0:42:55.587563]
>
> So I see I'm between Mike and Shalin in terms of how fast my machine
> goes
>
> On Mon, Jan 18, 2016 at 8:58 AM, Shalin Shekhar Mangar
>
Thanks for waiting Adrien. I have now backported SOLR-8418 to 5.4.
On Sun, Jan 17, 2016 at 10:01 PM, Adrien Grand wrote:
> Le dim. 17 janv. 2016 à 04:00, Mark Miller a
> écrit :
>
>> Always nice to be patient and accommodating for reroll 1. You know,
I missed the initial RC, but if we are going to re-spin (and looks like
Yonik has a patch up now), I would like to back-port SOLR-8418. Should be
fairly benign, let me know if there are any concerns..
On Fri, Jan 15, 2016 at 5:59 PM, Adrien Grand wrote:
> Thanks Yonik, let's
Looks like my bad on merge to branch 5x. I should be near a computer in a
few hours, and will fix it then if no one else gets to it by then..
On Fri, 1 Jan 2016 13:01 Policeman Jenkins Server
wrote:
> Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/15104/
>
Congratulations Tomas :)
On 6 Nov 2015 09:53, "Anshum Gupta" wrote:
> I'm pleased to announce that Tomás Fernández Löbbe has accepted the PMC’s
> invitation to join.
>
> Welcome Tomás!
>
> --
> Anshum Gupta
>
Congratulations and welcome :)
On 6 Nov 2015 15:19, "Joel Bernstein" wrote:
> I'm pleased to announce that Dennis Gove has accepted the PMC's
> invitation to become a committer.
>
> Dennis, it's tradition that you introduce yourself with a brief bio.
>
> Your account is not
Crickets..
I have raised https://issues.apache.org/jira/browse/SOLR-7932 anyway for
this issue..
On Sat, Aug 8, 2015 at 8:50 PM, Ramkumar R. Aiyengar
andyetitmo...@gmail.com wrote:
Noticed while looking at https://issues.apache.org/jira/browse/SOLR-7859
that wall time recorded as commit data
I wonder if there might be value in BitDocIdSet.Builder which Lucene uses.
It had perf issues of its soon, but LUCENE-6645 seems to have fixed them,
and it does a similar approach as above (int array and then fixedbitset).
On 3 Aug 2015 12:35, Toke Eskildsen t...@statsbiblioteket.dk wrote:
On
Noticed while looking at https://issues.apache.org/jira/browse/SOLR-7859
that wall time recorded as commit data on a commit to check if replication
needs to be done. In IndexFetcher, there is this code:
if (!forceReplication
IndexDeletionPolicyWrapper.getCommitTimestamp(commit) ==
: Strange comment in CdcrReplicationHandlerTest.java
Yeah, I wondered that myself.
On Wed, Jul 29, 2015 at 1:35 PM, Ramkumar R. Aiyengar
andyetitmo...@gmail.com wrote:
Hmm.. I would have expected rat to fail this in precommit actually..
On 29 Jul 2015 18:01, Timothy Potter thelabd
Hmm.. I would have expected rat to fail this in precommit actually..
On 29 Jul 2015 18:01, Timothy Potter thelabd...@gmail.com wrote:
Why is this in the code?
/**
* Copyright (c) 2015 Renaud Delbru. All Rights Reserved.
*/
package org.apache.solr.cloud;
Welcome Christine. Glad to have company a couple of desks away :)
On 24 Jul 2015 08:28, Adrien Grand jpou...@gmail.com wrote:
I'm pleased to announce that Christine Poerschke has accepted the PMC's
invitation to become a committer.
Christine, it's tradition that you introduce yourself with a
Welcome Mikhail!
On Tue, Jul 21, 2015 at 8:21 AM, Adrien Grand jpou...@gmail.com 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
Welcome Upayavira!
On 22 Jun 2015 20:02, Steve Rowe sar...@gmail.com wrote:
I'm pleased to announce that Upayavira has accepted the PMC's invitation
to become a committer.
Upayavira, it's tradition that you introduce yourself with a brief bio.
Mike McCandless, the Lucene PMC chair, has
On Fri, Jun 12, 2015 at 8:09 PM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
FAILED: org.apache.solr.cloud.FullSolrCloudDistribCmdsTest.test
Error Message:
Invalid content type:
Stack Trace:
org.apache.http.ParseException: Invalid content type:
at
Could we change the CHANGES.txt links with the .html links instead? They
are much better formatted.
(I just realised I don't have edit access to the wiki, could someone add
me? Name: Ramkumar Aiyengar, Alias: andyetitmoves)
I’ve made drafts for the Lucene and Solr release notes - please feel free
There is only one good rule though - no merge commmits in the history :)
Ever. Do whatever you want beyond that. A clean, simple history for each
branch is the only sensible use of Git I've seen.
+1
- Mark
On Sat, May 30, 2015 at 9:00 AM Adrien Grand jpou...@gmail.com wrote:
The main
+1
SUCCESS! [1:45:08.193859]
On Mon, Jun 1, 2015 at 10:49 PM, Shalin Shekhar Mangar
shalinman...@gmail.com wrote:
+1
Java7: SUCCESS! [1:16:45.996357]
Java8: SUCCESS! [1:29:39.782174]
On Mon, Jun 1, 2015 at 2:21 AM, Anshum Gupta ans...@anshumgupta.net
wrote:
Please vote for the third
+1 for git, great for working on multiple things at once.
Side note: git-svn is also not great btw for the kind of merging we need to
do with every commit, it kind of works but with too many caveats.
On the note that git clone is slow, sure, because it fetches a fair amount
of history which svn
, but this works just fine in general.
On the other hand git downloads gigabytes, before you can even get started.
Something needs to be done about all those jars in the source history,
I will not let this go.
On Sun, May 31, 2015 at 9:16 AM, Ramkumar R. Aiyengar
andyetitmo...@gmail.com
FYI.. We had considered moving to Jetty 9.3 in Solr for a few features
(HTTP/2), looks like that would force us to use Java 8.
May be a step closer to us thinking of a cutover ourselves..
-- Forwarded message --
From: Jesse McConnell jesse.mcconn...@gmail.com
Date: 27 May 2015
, Ramkumar R. Aiyengar
andyetitmo...@gmail.com wrote:
Curious.. sarowe, what's the spec?
On 26 May 2015 20:41, Anshum Gupta ans...@anshumgupta.net wrote:
The last buch of fixes seems to have fixed this. The tests passed on a
Jenkins that had failing tests earlier.
Thanks Steve Rowe for lending
Curious.. sarowe, what's the spec?
On 26 May 2015 20:41, Anshum Gupta ans...@anshumgupta.net wrote:
The last buch of fixes seems to have fixed this. The tests passed on a
Jenkins that had failing tests earlier.
Thanks Steve Rowe for lending the super-powerful machine that runs the
entire
Congratulations Tim!
On 26 May 2015 16:10, Steve Rowe sar...@gmail.com wrote:
I'm pleased to announce that Timothy Potter has accepted the PMC’s
invitation to join.
Welcome Tim!
Steve
-
To unsubscribe, e-mail:
On Thu, May 21, 2015 at 6:40 PM, Yonik Seeley ysee...@gmail.com wrote:
It's my opinion that it also wastes everyones time to force them to
have a pristine checkout before committing
I guess there are two kinds of checks which `ant precommit` tries to
combine -- one is checks which influence
+1
SUCCESS! [1:28:45.828215]
On Fri, Apr 10, 2015 at 2:05 PM, Joel Bernstein joels...@gmail.com wrote:
+1
SUCCESS! [0:40:41.211133]
Joel Bernstein
http://joelsolr.blogspot.com/
On Fri, Apr 10, 2015 at 8:22 AM, Dawid Weiss dawid.we...@cs.put.poznan.pl
wrote:
+1
SUCCESS!
May be we should forbid calls to the two argument version of Paths.get.
Especially given other wishes as well apart from Hdfs (like to use a
different filesystem for tests), this call, which uses the default
filesystem, seems to be a mistake waiting to happen..
On 9 Apr 2015 07:48, Varun Thacker
I meant the *multiple* arg Paths.get.. (its a vararg function)
On 9 Apr 2015 08:09, Ramkumar R. Aiyengar andyetitmo...@gmail.com wrote:
May be we should forbid calls to the two argument version of Paths.get.
Especially given other wishes as well apart from Hdfs (like to use a
different
work currently anyway. If I shouldn't, please speak up now..
On 4 Apr 2015 00:39, Ramkumar R. Aiyengar andyetitmo...@gmail.com wrote:
I started looking at porting cloud-dev scripts to the new startup scripts
after the discussion at SOLR-7240, but wasn't quite sure of what the
behaviour should
I started looking at porting cloud-dev scripts to the new startup scripts
after the discussion at SOLR-7240, but wasn't quite sure of what the
behaviour should be, having never used them myself. Some of the scripts
there have syntax errors, and I am not sure if some of the others are doing
what
Sounds good to me, except that we have to reconcile some of the objections
in the past to collection API additions, like with
https://issues.apache.org/jira/SOLR-6278
In short, collection API provides you a way to operate on collections.
Operationally you would often also want functionality based
Thanks again Shalin.. You would have thought I would learn from doing this
mistake once, and not repeat it for the merge! :)
On 28 Mar 2015 00:13, Shalin Shekhar Mangar shalinman...@gmail.com
wrote:
I committed a fix.
On Fri, Mar 27, 2015 at 4:01 PM, Policeman Jenkins Server
proposal.
Best,
Erick
On Wed, Mar 25, 2015 at 7:34 AM, Shawn Heisey apa...@elyograg.org wrote:
On 3/25/2015 3:24 AM, Ramkumar R. Aiyengar wrote:
I know patches are generally for bug fixes, but given that it is the end
of line branch for 4x, do we accommodate requests for back porting
Thanks Shalin!
On 25 Mar 2015 01:39, Shalin Shekhar Mangar shalinman...@gmail.com
wrote:
I committed a fix.
On Tue, Mar 24, 2015 at 6:02 PM, Policeman Jenkins Server
jenk...@thetaphi.de wrote:
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/12076/
Java: 64bit/jdk1.8.0_40
I know patches are generally for bug fixes, but given that it is the end of
line branch for 4x, do we accommodate requests for back porting small
features, or just ask them to patch it themselves?
-- Forwarded message --
From: domenkozar g...@git.apache.org
Date: 25 Mar 2015 09:17
On 16 Mar 2015 22:51, Shawn Heisey apa...@elyograg.org wrote:
I have some changes I'd like to make to the Solr website, but I'm not
entirely sure what kind of review process that should go through.
Should I open an issue in Jira, or just discuss it here?
Given that this is version controlled
Happened to notice that the 'default locale' used by QueryParserBase
is `Locale.getDefault()`, on which we call things like `toLowerCase`
etc. Given that we forbid functions like `toLowerCase` with no args,
does anyone know why we don't use the root locale as the default as
opposed to the system
to true which makes the
indexing thread hang during connection loss events.
On Sat, Mar 14, 2015 at 4:57 AM, Ramkumar R. Aiyengar
andyetitmo...@gmail.com wrote:
I haven't tested this, but something which I observed looking at the LIR
code. If there's a ZK election or connection loss
I haven't tested this, but something which I observed looking at the LIR
code. If there's a ZK election or connection loss, and the leader is unable
to reach a replica, would it stall till the ZK connection is established,
due to the LIR process? I can't see it happening in the background, may be
That explains a lot. Thanks Mike!
On 13 Mar 2015 00:46, Michael McCandless luc...@mikemccandless.com
wrote:
On Thu, Mar 12, 2015 at 5:38 PM, Yonik Seeley ysee...@gmail.com wrote:
On Thu, Mar 12, 2015 at 8:04 PM, Ramkumar R. Aiyengar
andyetitmo...@gmail.com wrote:
This actually brings me
This actually brings me to a question I have had for a while. Why do we
check in auto generated code? Shouldn't the build system run javacc as a
prereq to compiling instead?
On 12 Mar 2015 18:08, Alan Woodward a...@flax.co.uk wrote:
Ah, OK. Sorry for the noise!
On 12 Mar 2015, at 15:19, Yonik
Without commenting on if we should do it (personally I am for it, but I am
also sympathetic to people who feel it's excessive to mandate it), if we
are going down this road, might be worth looking at standalone tools like
astyle which do this rather than an IDE. Some advantages:
* You can easily
Thanks all, I have now added the changes entry.
On Wed, Mar 4, 2015 at 10:23 PM, Chris Hostetter hossman_luc...@fucit.org
wrote:
: The change had no functional impact, hence left it alone.
:
: But happy to follow whatever is the existing practice. Should I have one
: for every change?
The change had no functional impact, hence left it alone.
But happy to follow whatever is the existing practice. Should I have one
for every change?
On Wed, Mar 4, 2015 at 8:29 PM, Alan Woodward a...@flax.co.uk wrote:
Hi Ram, I think you missed a CHANGES.txt entry on this one?
Alan Woodward
are fairly low (but non-zero, if you’ve ever
spent any quality time with tcpdump/wireshark).
Still, in a production setting, SIGKILL (aka “kill -9”) should be a last
resort after more reasonable methods (e.g. SIGINT, SIGTERM, SIGSTOP) have
failed.
*From:* Ramkumar R. Aiyengar
:* Ramkumar R. Aiyengar [mailto:andyetitmo...@gmail.com]
*Sent:* Saturday, February 28, 2015 8:15 PM
*To:* dev@lucene.apache.org
*Subject:* Re: reuseAddress default in Solr jetty.xml
Hey Charles, see my explanation above on why this is needed. If Solr has to
be killed, it would generally
Thanks everyone!
I lead the News Search backend team at the London RD office of Bloomberg.
I have been at this job for a little more than 7 years, and joined straight
from my university at IIT Madras, Chennai, India where I did my bachelors
and masters in CS. I started working with Lucene/Solr
*To:* dev@lucene.apache.org
*Subject:* Re: reuseAddress default in Solr jetty.xml
+1
- Mark
On Thu, Feb 26, 2015 at 1:54 PM Ramkumar R. Aiyengar
andyetitmo...@gmail.com wrote:
The jetty.xml we currently ship by default doesn't set reuseAddress=true.
If you are having a bad GC day
The jetty.xml we currently ship by default doesn't set reuseAddress=true.
If you are having a bad GC day with things going OOM and resulting in Solr
not even being able to shutdown cleanly (or the oom_solr.sh script killing
it), whatever external service management mechanism you have is probably
I have seen this happen before and reached out to infra guys. Invariably it
seems to fix by itself at some point, but till then, git svn rebase ends up
taking all the memory that's available and dies, whatever they try. There
are some known issues with git-svn memory usage on commits to large
It would be good to have a link to changes.html (like
https://lucene.apache.org/core/4_10_3/changes/Changes.html) (had suggested
this in previous releases)
On 23 Jan 2015 20:11, Anshum Gupta ans...@anshumgupta.net wrote:
I’ve made drafts for the Lucene and Solr release notes - please feel free
Would be great if someone is able to pick up the patch for SOLR-6902 soon,
it refactors Solr's distributed tests for easier testing.
The refactor however touches a hundred odd files, and attracts a lot of
conflicts with every passing day. Have just resolved conflicts in 30 odd
files and re-posted
Just curious since I see this come up once in a while. Doesn't Apache SVN
offer tweaking pre-commit hooks? Isn't this better checked there than
failing tests after the fact?
On 30 Dec 2014 08:35, Erik Hatcher erik.hatc...@gmail.com wrote:
I'll fix. Geez! :) sorry.
On Dec 30, 2014, at
Is RamUsageTester supposed to work for cases where direct memory is
allocated (like with ByteBuffer's)?
I had a made a change to use direct ByteBuffer's in an Accountable object
and adjusted ramBytesUsed to reflect the memory used, but that seems to
upset tests using RamUsageTester to compare
An another thing I found out after a bit of digging is that the language
compliance level setting in the Project SDK had to be set at 8, else it
fails compilation as we are already making use of the default methods
feature.
On 25 Nov 2014 03:38, david.w.smi...@gmail.com david.w.smi...@gmail.com
know
if it _does_ mind you)
having a collection of questions like this will be useful for
documentation
So could you add this to that JIRA?
Thanks!
Erick
On Sat, Nov 8, 2014 at 4:24 PM, Ramkumar R. Aiyengar
andyetitmo...@gmail.com wrote:
Was trying out the example with the new layout
Was trying out the example with the new layout for the first time. Had
heard about issues with stray files lying around with this new layout on
the list, so I started with a fresh checkout.
Did:
$ cd solr
$ ant dist
...
$ bin/solr start
Waiting to see Solr listening on port 8983bin/solr: line
with `ant beast`
:
: I think ‘ant beast’ only works in the directory of the module
containing the
: test, not at a higher level.
:
: On Sep 19, 2014, at 11:45 AM, Ramkumar R. Aiyengar
: andyetitmo...@gmail.com wrote:
:
: I am trying to use `ant beast` on trunk (per
I am trying to use `ant beast` on trunk (per the recommendation in
test-help) and getting this error:
~/lucene-solr/lucene ant beast -Dbeast.iters=10 -Dtests.dups=6
-Dtestcase=TestBytesStore
-beast:
[beaster] Beast round: 1
BUILD FAILED
~/lucene-solr/lucene/common-build.xml:1363: The
Aha.. That worked, thanks!
On Fri, Sep 19, 2014 at 4:53 PM, Steve Rowe sar...@gmail.com wrote:
I think ‘ant beast’ only works in the directory of the module containing
the test, not at a higher level.
On Sep 19, 2014, at 11:45 AM, Ramkumar R. Aiyengar
andyetitmo...@gmail.com wrote:
I am
That sounds good. Btw, I first tried it at the toplevel, and that came back
with a beast target not found, hence went to lucene subdir. At least that's
guessable, so less important, would be to add that failure message to the
toplevel as well..
On 19 Sep 2014 18:02, Ryan Ernst r...@iernst.net
Have a few Solr patches which have been around for a while, could some one
please take a look and commit, or let me know if anything else is needed?
SOLR-6459 https://issues.apache.org/jira/browse/SOLR-6459 Consistently
log all Overseer operations, and queue size
SOLR-6454
Just curious, is there any case where you might genuinely need non-final
static members in a test class? I guess it wouldn't catch all cases, but
something in setup/teardown which bans that using introspection might catch
at least the obvious cases..
On 1 Sep 2014 14:01, Dawid Weiss
On Mon, Sep 1, 2014 at 8:54 PM, Dawid Weiss dawid.we...@cs.put.poznan.pl
wrote:
To be honest you shouldn't have any static initializers at all,
including final fields (unless they're really immutable, simple data
types). The reason for this is that static initializers (including
those for
I am in the process of looking at some of the ERROR level log output coming
from Solr to set up alarms, but currently the severity of what ERROR means
is kind of mixed across the code base. I am happy to fix this where I find,
but some guidance on what the various levels mean would be helpful.
which
adds to the spam.
In any case, I will probably first start with ERROR and WAR...
On Mon, Aug 25, 2014 at 9:48 PM, Mark Miller markrmil...@gmail.com wrote:
On Aug 25, 2014, at 4:44 PM, Ramkumar R. Aiyengar
andyetitmo...@gmail.com wrote:
I am in the process of looking at some
Currently HttpShardHandlerFactory and DUH2 set socket and connection
timeouts to unlimited by default. Should there be some finite default
instead? With the current defaults, a machine crash for example will lead
to requests in progress hang and occupy threads till the process is shut
down, which
, 2014 at 7:46:36 AM, Ramkumar R. Aiyengar (
andyetitmo...@gmail.com) wrote:
Currently HttpShardHandlerFactory and DUH2 set socket and connection
timeouts to unlimited by default. Should there be some finite default
instead? With the current defaults, a machine crash for example will lead
, 2014 at 10:09:56 AM, Ramkumar R. Aiyengar (
andyetitmo...@gmail.com) wrote:
Currently when a replica is watching the current leader's ephemeral node
and the leader disappears, it runs the leadership check along with its
two
way peer sync, ZK update etc. on the ZK event thread where
Currently when a replica is watching the current leader's ephemeral node
and the leader disappears, it runs the leadership check along with its two
way peer sync, ZK update etc. on the ZK event thread where the watch was
fired.
What this means is that for instances with lots of cores, you would
+1. We are probably already breaching this with 256 shards, something we
are still investigating.
On the question of other limits, there's also the limit on how many threads
your OS can support, we have in the past hit 65k threads and errored out
because of 64 shards per machine, not sure as yet
Would someone have a few minutes to validate this race condition fix?
Thanks!
-- Forwarded message --
From: Ramkumar Aiyengar (JIRA) j...@apache.org
Date: 8 Jan 2014 16:49
Subject: [jira] [Created] (SOLR-5620) Race condition while setting
ZkStateReader.aliases
To:
Any time there's a release, I tend to look at the Changes.html file (
https://lucene.apache.org/solr/4_6_1/changes/Changes.html), it's a handy
link to look up the changes as soon as you get the mail, especially on
mobile. It would be nice if our release announcements had the link instead
of the
84 matches
Mail list logo