Re: [2/2] lucene-solr git commit: SOLR-8725: Fix precommit check

fixed On Thu, Mar 3, 2016 at 1:23 PM, wrote: > SOLR-8725: Fix precommit check > > > Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo > Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/73d2d112 > Tree:

Re: lucene-solr git commit: SOLR-8725: Allow hyphen in shard, collection, core, and alias names but not the first char

.txt > @@ -382,6 +382,8 @@ Other Changes > > * SOLR-8778: Deprecate CSVStrategy's setters, and make its pre-configured > strategies immutable. (Steve Rowe) > > +* SOLR-8725: Allow hyphen in collection, core, shard, and alias name as > the non-first character (Anshum Gupta) &

Re: Lucene/Solr 6.0.0 Release Branch

Sure, I will. Thanks ! On Thu, Mar 3, 2016 at 11:20 AM, Nicholas Knize <nkn...@gmail.com> wrote: > I quickly skimmed the patches. I'm OK with them being backported to 6.0. > Can you mark the Fix Version/s accordingly? > > Thanks! > > On Thu, Mar 3, 2016 at 1:

[jira] [Updated] (SOLR-8423) DELETESHARD should cleanup the instance and data directory, like DELETEREPLICA

[ https://issues.apache.org/jira/browse/SOLR-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8423: --- Fix Version/s: 6.0 master > DELETESHARD should cleanup the instance and d

[jira] [Updated] (SOLR-8725) Cores, collections, and shards should accept hyphens in identifier name

[ https://issues.apache.org/jira/browse/SOLR-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8725: --- Fix Version/s: 6.0 master > Cores, collections, and shards should accept hyph

Re: Lucene/Solr 6.0.0 Release Branch

threads. (Sorry, I haven’t gone back and >> found the exact messages that left me with this impression, so I guess I >> could be wrong.) >> >> One of the RM’s most important responsibilities is timely communication. >> If you’re going to be AFK for extended periods, please let people know. >> >> -- >> Steve >> www.lucidworks.com >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> >> > -- Anshum Gupta

Re: Lucene/Solr 6.0.0 Release Branch

> >>>>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > >>>>>> For additional commands, e-mail: dev-h...@lucene.apache.org > >>>>>> > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> Regards, > >>>>> Shalin Shekhar Mangar. > >>>>> > >>>>> - > >>>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > >>>>> For additional commands, e-mail: dev-h...@lucene.apache.org > >>>>> > >>>> > >>>> - > >>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > >>>> For additional commands, e-mail: dev-h...@lucene.apache.org > >>>> > >>> > >>> > >>> > >>> -- > >>> Regards, > >>> Shalin Shekhar Mangar. > >> > >> > >> > >> -- > >> Regards, > >> Shalin Shekhar Mangar. > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > >> For additional commands, e-mail: dev-h...@lucene.apache.org > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: dev-h...@lucene.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > -- Anshum Gupta

[jira] [Commented] (SOLR-8725) Cores, collections, and shards should accept hyphens in identifier name

[ https://issues.apache.org/jira/browse/SOLR-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15176785#comment-15176785 ] Anshum Gupta commented on SOLR-8725: Yes, we should back-port this to a 5x release whenever

[jira] [Updated] (SOLR-8725) Cores, collections, and shards should accept hyphens in identifier name

[ https://issues.apache.org/jira/browse/SOLR-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8725: --- Attachment: SOLR-8725.patch [~gerlowskija] yes, it makes sense to consolidate all the messages in one

[jira] [Commented] (SOLR-8097) Implement a builder pattern for constructing a Solrj client

[ https://issues.apache.org/jira/browse/SOLR-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15176292#comment-15176292 ] Anshum Gupta commented on SOLR-8097: Seems like there's some issue with the patch as it has .orig files

[jira] [Commented] (SOLR-8097) Implement a builder pattern for constructing a Solrj client

[ https://issues.apache.org/jira/browse/SOLR-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15176276#comment-15176276 ] Anshum Gupta commented on SOLR-8097: Thanks Jason. Looking at it now. Let's not move all the tests

[jira] [Assigned] (SOLR-8423) DELETESHARD should cleanup the instance and data directory, like DELETEREPLICA

[ https://issues.apache.org/jira/browse/SOLR-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reassigned SOLR-8423: -- Assignee: Anshum Gupta > DELETESHARD should cleanup the instance and data directory, l

[jira] [Updated] (SOLR-8423) DELETESHARD should cleanup the instance and data directory, like DELETEREPLICA

[ https://issues.apache.org/jira/browse/SOLR-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8423: --- Attachment: SOLR-8423.patch Patch with tests. I'll commit this once the 6.0 work is in place

[jira] [Assigned] (SOLR-8725) Cores, collections, and shards should accept hyphens in identifier name

[ https://issues.apache.org/jira/browse/SOLR-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reassigned SOLR-8725: -- Assignee: Anshum Gupta > Cores, collections, and shards should accept hyphens in identif

[jira] [Updated] (SOLR-8725) Cores, collections, and shards should accept hyphens in identifier name

[ https://issues.apache.org/jira/browse/SOLR-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8725: --- Attachment: SOLR-8725.patch Patch without tests. Will add them in a bit and commit. This allows

[jira] [Updated] (SOLR-8725) Cores, collections, and shards should accept hyphens in identifier name

[ https://issues.apache.org/jira/browse/SOLR-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8725: --- Summary: Cores, collections, and shards should accept hyphens in identifier name (was: Invalid name

[jira] [Commented] (SOLR-8725) Invalid name error with core names with hyphens

[ https://issues.apache.org/jira/browse/SOLR-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15169804#comment-15169804 ] Anshum Gupta commented on SOLR-8725: After discussions on other JIRAs mentioned above, I'll add

Re: Rolling upgrades from 5.x to 6.0

release >>>> that will allow rolling upgrades (like the 5.4.1 fix that allowed rolling >>>> upgrades from pre-5.4 to 5.4)? >>>> >>>> I feel it's odd (and may not be taken well) if we force users to take >>>> down their entire cluster if they want to upgrade to 6.0. Definitely feels >>>> like it will also slow down 6.0 adoption. >>>> >>>> And if nothing can be done, what's the recommended way then to upgrade >>>> to 6.0? >>>> >>>> Shai >>>> >>> -- >>> - Mark >>> about.me/markrmiller >>> >> > -- Anshum Gupta

Re: Removing branch_5x shortly

gt; format changes. It's beyond simple for those people to understand once the >> next major version is released, don't put any more index format changes >> into the previous line. >> >> That is a very weak technical argument. Committers already have to >> remember how to deal with back compat and what changes can happen when. >> This is no different. >> >> - Mark >> -- >> - Mark >> about.me/markrmiller >> > -- > - Mark > about.me/markrmiller > -- Anshum Gupta

[jira] [Comment Edited] (SOLR-8110) Start enforcing field naming recomendations in next X.0 release?

[ https://issues.apache.org/jira/browse/SOLR-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159191#comment-15159191 ] Anshum Gupta edited comment on SOLR-8110 at 2/23/16 5:06 PM: - I personally

[jira] [Commented] (SOLR-8110) Start enforcing field naming recomendations in next X.0 release?

[ https://issues.apache.org/jira/browse/SOLR-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159191#comment-15159191 ] Anshum Gupta commented on SOLR-8110: I personally would prefer the more invasive approach here. bq

Re: Removing branch_5x shortly

t > of > > 5.x is really there or not. > > > > I say all of this presuming that 6.0 is imminent within the next few > weeks. > > It seems reasonable to have feature releases (minor releases) on a > monthly > > basis, so if 6.0 is not out a month from now, then a

[jira] [Commented] (SOLR-8110) Start enforcing field naming recomendations in next X.0 release?

[ https://issues.apache.org/jira/browse/SOLR-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159127#comment-15159127 ] Anshum Gupta commented on SOLR-8110: bq. But UNDERSCORE, DASH and DOT should be supported, i.e. [A-Za

Re: Removing branch_5x shortly

ot;semantic" >>> names for branches -- they're kind of hard to eradicate once created >>> in public. >>> >>> Anyway, as for branch_5x -- no need to protect anything, really. If >>> somebody DOES commit something (by accident or otherwise) we can >>> always revert those commits (or even force the reference to what it >>> was before the mistake, effectively undoing the change). >>> >>> D. >>> >>> -- >>> >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >>> For additional commands, e-mail: dev-h...@lucene.apache.org >>> >>> >> -- >> Uwe Schindler >> H.-H.-Meier-Allee 63, 28213 Bremen >> http://www.thetaphi.de >> > -- Anshum Gupta

Re: VOTE: RC1 Release apache-solr-ref-guide-5.5.pdf

I think going forward, we should change the command to reflect the correct tgz file name in the 'Installing Solr' section for the ref guide. On Mon, Feb 22, 2016 at 10:54 AM, Anshum Gupta <ans...@anshumgupta.net> wrote: > +1. Looks good to me. > > Thanks Hoss! > > On Fri, Fe

Re: VOTE: RC1 Release apache-solr-ref-guide-5.5.pdf

ef-guide/apache-solr-ref-guide-5.5-RC1/ > > -Hoss > http://www.lucidworks.com/ > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > -- Anshum Gupta

[jira] [Commented] (SOLR-8110) Start enforcing field naming recomendations in next X.0 release?

[ https://issues.apache.org/jira/browse/SOLR-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157475#comment-15157475 ] Anshum Gupta commented on SOLR-8110: I am sure there would be reasons for people to use field names

[jira] [Commented] (SOLR-8097) Implement a builder pattern for constructing a Solrj client

[ https://issues.apache.org/jira/browse/SOLR-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157463#comment-15157463 ] Anshum Gupta commented on SOLR-8097: Thanks Hoss. I'll work on adding support for this in SOLR-6312

[jira] [Commented] (SOLR-8097) Implement a builder pattern for constructing a Solrj client

[ https://issues.apache.org/jira/browse/SOLR-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157394#comment-15157394 ] Anshum Gupta commented on SOLR-8097: Ah ok. I was just looking at the code and it might just be an idea

[jira] [Commented] (SOLR-8097) Implement a builder pattern for constructing a Solrj client

[ https://issues.apache.org/jira/browse/SOLR-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157365#comment-15157365 ] Anshum Gupta commented on SOLR-8097: I think we should not use 'prefer' as it's not a preference

[jira] [Assigned] (SOLR-8097) Implement a builder pattern for constructing a Solrj client

[ https://issues.apache.org/jira/browse/SOLR-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reassigned SOLR-8097: -- Assignee: Anshum Gupta > Implement a builder pattern for constructing a Solrj cli

[jira] [Commented] (SOLR-8097) Implement a builder pattern for constructing a Solrj client

[ https://issues.apache.org/jira/browse/SOLR-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157327#comment-15157327 ] Anshum Gupta commented on SOLR-8097: Thanks Jason. This looks good to me, how ever I'm debating about

[jira] [Commented] (SOLR-8097) Implement a builder pattern for constructing a Solrj client

[ https://issues.apache.org/jira/browse/SOLR-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15156283#comment-15156283 ] Anshum Gupta commented on SOLR-8097: I'll take a look tomorrow as I'd be away from the computer

Re: Removing branch_5x shortly

n previous major releases. > There was already even a lot of work toward 4.11 when the deletion > happened IIRC. > > -Yonik > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > -- Anshum Gupta

[jira] [Resolved] (SOLR-8705) ERROR while indexing/updating record

[ https://issues.apache.org/jira/browse/SOLR-8705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-8705. Resolution: Incomplete > ERROR while indexing/updating rec

[jira] [Resolved] (SOLR-8704) ERROR while indexing/updating record

[ https://issues.apache.org/jira/browse/SOLR-8704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-8704. Resolution: Invalid The right place to ask about such errors is not JIRA but the solr user mailing

[jira] [Resolved] (SOLR-8703) ERROR

[ https://issues.apache.org/jira/browse/SOLR-8703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-8703. Resolution: Invalid > ERROR > -- > > Key: SOLR-8703 >

Re: [JENKINS] Lucene-Solr-trunk-MacOSX (64bit/jdk1.8.0) - Build # 3095 - Still Failing!

This should be fixed now. On Thu, Feb 18, 2016 at 6:46 PM, Policeman Jenkins Server < jenk...@thetaphi.de> wrote: > Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/3095/ > Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseG1GC > > 3 tests failed. > FAILED: >

Re: lucene-solr git commit: SOLR-8677: Restrict creation of shards with invalid names

ke, hossmann, Tomás Fernández Löbbe, Shai Erera) > > +Other Changes > +------ > +* SOLR-8677: Prevent shards containing invalid characters from being > created. Checks added server-side > + and in SolrJ. (Shai Erera, Jason Gerlowski, Anshum Gupta) > + >

[jira] [Updated] (SOLR-8677) SOLR allows creation of shards with invalid names.

[ https://issues.apache.org/jira/browse/SOLR-8677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8677: --- Attachment: SOLR-8677.patch There were a few issues with the last patch. Here's an updated patch. I'll

[jira] [Updated] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8619: --- Attachment: SOLR-8619-test.patch A test that shows what's going on. > A new replica should not bec

Re: [VOTE] Release Lucene/Solr 5.5.0 RC3

plenty of time to chew on them. > > Mike McCandless > > http://blog.mikemccandless.com > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > -- Anshum Gupta

[jira] [Commented] (SOLR-8677) SOLR allows creation of shards with invalid names.

[ https://issues.apache.org/jira/browse/SOLR-8677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15149451#comment-15149451 ] Anshum Gupta commented on SOLR-8677: bq. This obviously means some duplicated code, since the classes

[jira] [Updated] (SOLR-8677) SOLR allows creation of shards with invalid names.

[ https://issues.apache.org/jira/browse/SOLR-8677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8677: --- Attachment: SOLR-8677.patch Thanks Jason. Here's an updated patch. * Refactored the validator

[jira] [Updated] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8619: --- Priority: Major (was: Blocker) > A new replica should not become leader when all current repli

Re: confluence line spacing

see the XHTML > source. > > On Tue, Feb 9, 2016 at 3:13 PM, Anshum Gupta <ans...@anshumgupta.net> > wrote: > >> I just added documentation for DELETESTATUS API on the CollectionsAdmin >> page in the ref guide but couldn't get the line spacing to be the

[jira] [Updated] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8619: --- Priority: Blocker (was: Major) > A new replica should not become leader when all current repli

Re: Lucene/Solr 6.0.0 release

ust getting all the (stable) backported features > > out to the world before we release 6.0.0. > > > > I'll aim to cut the 5.5 branch mid next week... > > > > Mike McCandless > > > > http://blog.mikemccandless.com > > > > > > On Thu, Feb

[jira] [Updated] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8619: --- Fix Version/s: 5.5 > A new replica should not become leader when all current replicas are d

[jira] [Resolved] (SOLR-8648) Support selective clearing up of stored async collection API responses

[ https://issues.apache.org/jira/browse/SOLR-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-8648. Resolution: Fixed > Support selective clearing up of stored async collection API respon

[jira] [Updated] (SOLR-8648) Support selective clearing up of stored async collection API responses

[ https://issues.apache.org/jira/browse/SOLR-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8648: --- Fix Version/s: Trunk 5.5 > Support selective clearing up of stored async collect

[jira] [Commented] (SOLR-8097) Implement a builder pattern for constructing a Solrj client

[ https://issues.apache.org/jira/browse/SOLR-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15139189#comment-15139189 ] Anshum Gupta commented on SOLR-8097: Thanks for the patch Jason. The patch doesn't apply cleanly

[jira] [Commented] (SOLR-8534) Add generic support for Collection APIs to be async

[ https://issues.apache.org/jira/browse/SOLR-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15139156#comment-15139156 ] Anshum Gupta commented on SOLR-8534: Instead of duplicating async code for async why not add another

Re: [1/2] lucene-solr git commit: SOLR-6594 Mark old schema APIs as deprecated

1,7 +431,12 @@ public class RestManager { > throw new ResourceException(Status.CLIENT_ERROR_BAD_REQUEST, > errMsg, ioExc); >} >return parsedJson; > -} > +} > + > +@Override > +protected void addDeprecatedWarning() { > + //this is not deprecated > +} >} // end ManagedEndpoint class > >/** > @@ -788,5 +793,5 @@ public class RestManager { > if > (ManagedResource.ChildResourceSupport.class.isAssignableFrom(res.getClass())) > { >router.attach(path+"/{child}", res.getServerResourceClass()); > } > - } > + } > } > > -- Anshum Gupta

confluence line spacing

I just added documentation for DELETESTATUS API on the CollectionsAdmin page in the ref guide but couldn't get the line spacing to be the same as the rest of the lines. Is there something I'm missing? -- Anshum Gupta

[jira] [Updated] (SOLR-8648) Support selective clearing up of stored async collection API responses

[ https://issues.apache.org/jira/browse/SOLR-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8648: --- Attachment: SOLR-8648.patch the previous patch had some rebase issues, here's another clean one

[jira] [Updated] (SOLR-8648) Support selective clearing up of stored async collection API responses

[ https://issues.apache.org/jira/browse/SOLR-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8648: --- Attachment: SOLR-8648.patch Thanks for the review Shai. Here's an updated patch that addresses your

[jira] [Commented] (SOLR-8648) Support selective clearing up of stored async collection API responses

[ https://issues.apache.org/jira/browse/SOLR-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137672#comment-15137672 ] Anshum Gupta commented on SOLR-8648: Also, about the deprecation, I'll change the 5x commit to actually

[jira] [Updated] (SOLR-8648) Support selective clearing up of stored async collection API responses

[ https://issues.apache.org/jira/browse/SOLR-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8648: --- Attachment: SOLR-8648.patch Updated patch. Seems like my idea settings file is acting up. Hopefully

[jira] [Comment Edited] (SOLR-8648) Support selective clearing up of stored async collection API responses

[ https://issues.apache.org/jira/browse/SOLR-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137510#comment-15137510 ] Anshum Gupta edited comment on SOLR-8648 at 2/8/16 7:23 PM: Thanks

[jira] [Commented] (SOLR-8534) Add generic support for Collection APIs to be async

[ https://issues.apache.org/jira/browse/SOLR-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137889#comment-15137889 ] Anshum Gupta commented on SOLR-8534: Thanks [~varunthacker] ! I'll take a look in a couple of hours

[jira] [Commented] (SOLR-8642) SOLR allows creation of collections with invalid names

[ https://issues.apache.org/jira/browse/SOLR-8642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15135056#comment-15135056 ] Anshum Gupta commented on SOLR-8642: Thanks for the patch Jason. Here's some feedback: * Why don't we

[jira] [Commented] (SOLR-8534) Add generic support for Collection APIs to be async

[ https://issues.apache.org/jira/browse/SOLR-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134429#comment-15134429 ] Anshum Gupta commented on SOLR-8534: this has added async support to 'requeststatus' call, which isn't

[jira] [Created] (SOLR-8648) Support selective clearing up of stored async collection API responses

Anshum Gupta created SOLR-8648: -- Summary: Support selective clearing up of stored async collection API responses Key: SOLR-8648 URL: https://issues.apache.org/jira/browse/SOLR-8648 Project: Solr

[jira] [Commented] (SOLR-8534) Add generic support for Collection APIs to be async

[ https://issues.apache.org/jira/browse/SOLR-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134682#comment-15134682 ] Anshum Gupta commented on SOLR-8534: Also, this would be a problem with everything that doesn't go

[jira] [Commented] (SOLR-8534) Add generic support for Collection APIs to be async

[ https://issues.apache.org/jira/browse/SOLR-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134653#comment-15134653 ] Anshum Gupta commented on SOLR-8534: Sorry for not clarifying but I'm actually talking about the SolrJ

[jira] [Updated] (SOLR-8648) Support selective clearing up of stored async collection API responses

[ https://issues.apache.org/jira/browse/SOLR-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8648: --- Attachment: SOLR-8648.patch Patch with test > Support selective clearing up of stored as

[jira] [Commented] (SOLR-8575) Fix HDFSLogReader replay status numbers and a performance bug where we can reopen FSDataInputStream too often.

[ https://issues.apache.org/jira/browse/SOLR-8575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133372#comment-15133372 ] Anshum Gupta commented on SOLR-8575: Hey [~markrmil...@gmail.com] is the commit supposed to be from

[jira] [Commented] (SOLR-8575) Fix HDFSLogReader replay status numbers and a performance bug where we can reopen FSDataInputStream too often.

[ https://issues.apache.org/jira/browse/SOLR-8575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133649#comment-15133649 ] Anshum Gupta commented on SOLR-8575: Thanks Uwe! Do you mean to say there's already an open issue

Re: Lucene/Solr 6.0.0 release

> Remains >> > to be seen how fast INFRA reacts for us though. >> > >> > There will also probably be a bit to do as we work through the first >> > release, in terms of release scripts, docs, etc. I think most of it >> should >> > be fairly light weight changes though. >> > >> > - Mark >> > -- >> > - Mark >> > about.me/markrmiller >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> >> > -- Anshum Gupta

[jira] [Commented] (LUCENE-7012) Change eclipse's "New Java Files" template to place the license header before the package declaration

[ https://issues.apache.org/jira/browse/LUCENE-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130699#comment-15130699 ] Anshum Gupta commented on LUCENE-7012: -- Thanks Shai. LGTM, would be good to have this for idea too

[jira] [Commented] (LUCENE-7012) Change Lucene/Solr IDE configs to place new Java files' license header before the package declaration

[ https://issues.apache.org/jira/browse/LUCENE-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130997#comment-15130997 ] Anshum Gupta commented on LUCENE-7012: -- Thanks Steve! > Change Lucene/Solr IDE configs to place

[jira] [Assigned] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reassigned SOLR-8619: -- Assignee: Anshum Gupta > A new replica should not become leader when all current repli

[jira] [Commented] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15125572#comment-15125572 ] Anshum Gupta commented on SOLR-8619: This makes sense, along with a check for new collection creation

[jira] [Commented] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123606#comment-15123606 ] Anshum Gupta commented on SOLR-8619: I think we could just reuse the lastPublished state instead

[jira] [Commented] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123616#comment-15123616 ] Anshum Gupta commented on SOLR-8619: But the user wouldn't get back a useable replica. We could add

[jira] [Commented] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123603#comment-15123603 ] Anshum Gupta commented on SOLR-8619: Sure, this should work. Might have to add a few checks

[jira] [Created] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

Anshum Gupta created SOLR-8619: -- Summary: A new replica should not become leader when all current replicas are down as it leads to data loss Key: SOLR-8619 URL: https://issues.apache.org/jira/browse/SOLR-8619

[jira] [Commented] (SOLR-8617) Add a wait for active option in to add replica

[ https://issues.apache.org/jira/browse/SOLR-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122253#comment-15122253 ] Anshum Gupta commented on SOLR-8617: Sure, though you could still achieve this via ADDREPLICA

[jira] [Commented] (SOLR-8617) Add a wait for active option in to add replica

[ https://issues.apache.org/jira/browse/SOLR-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1510#comment-1510 ] Anshum Gupta commented on SOLR-8617: We don't want for the same when we split shard either. Guess I'm

[jira] [Commented] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122707#comment-15122707 ] Anshum Gupta commented on SOLR-8619: What I have in mind should play nice with both of those things

[jira] [Commented] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122721#comment-15122721 ] Anshum Gupta commented on SOLR-8619: Sure, I strongly think we need to be intelligent in electing

Re: Shard splitting blocks the overseer queue for duration of split

dance from someone knowledgeable, both to make it more > solid, and also hopefully so it could be upstreamed. > > Thanks! > Scott > > -- Anshum Gupta

Releasing 5.3.2

as part of the release process in such cases. What do you guys think? -- Anshum Gupta

Re: Apache Lucene/Solr GIT migration, requesting infra help

e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > -- Anshum Gupta

[ANNOUNCE] Apache Solr 5.3.2 released

. -- Anshum Gupta

[ANNOUNCE] Apache Lucene 5.3.2 released

replicated the release yet. If that is the case, please try another mirror. This also goes for Maven access. -- Anshum Gupta

[jira] [Commented] (SOLR-8587) Add segments file information to core admin status

[ https://issues.apache.org/jira/browse/SOLR-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113961#comment-15113961 ] Anshum Gupta commented on SOLR-8587: +1 I think this makes sense, specially until we have backup

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Does anyone here know how to edit a log message after committing? I accidentally typed in lucene instead of solr for one of the release related commits. On Fri, Jan 22, 2016 at 11:03 AM, Anshum Gupta <ans...@anshumgupta.net> wrote: > Hi Adrien, > > I'm in the middle of publishin

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

nly remaining step that requires you to modify the code base). > > If you will not be able to do it by that time, I can take care of it, just > let me know. > -- Anshum Gupta

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

In the git world this would be possible (locally, with git commit > > --amend), but after you push to a remote repository this would be > > discouraged and the same way as above would be advised since other > > people might already be using your commit. > > > > D. > &g

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

f it, just > let me know. > -- Anshum Gupta

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

to save some > time and I wouldn't want the git mirror to be out of sync with SVN > content. > > Dawid > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > -- Anshum Gupta

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

I've added the back-compat indexes for 5.3.2 to lucene_solr_5_3, branch_5x, and trunk. Think we are good to go in terms the 5.3.2 release-svn dependency. On Fri, Jan 22, 2016 at 11:41 AM, Anshum Gupta <ans...@anshumgupta.net> wrote: > Adrien, > > Seems like I'd have to wait un

[jira] [Commented] (SOLR-8560) Add RequestStatusState enum

[ https://issues.apache.org/jira/browse/SOLR-8560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15111310#comment-15111310 ] Anshum Gupta commented on SOLR-8560: Thanks Shai. Looks good overall other than the following: * Why

[jira] [Commented] (SOLR-8560) Add RequestStatusState enum

[ https://issues.apache.org/jira/browse/SOLR-8560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15111959#comment-15111959 ] Anshum Gupta commented on SOLR-8560: +1 Thanks Shai. I wish we could be consistent in our header

Re: Question about release plans amidst the git transition

--- > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: dev-h...@lucene.apache.org > > > > ----- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > -- Anshum Gupta

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

<iori...@yahoo.com.invalid> wrote: > +1 > SUCCESS! [1:38:55.940645] > > > > > On Tuesday, January 19, 2016 10:25 PM, Yonik Seeley <ysee...@gmail.com> > wrote: > +1 > > -Yonik > > > > On Mon, Jan 18, 2016 at 11:23 AM, Anshum Gupta <ans...@a

Re: [VOTE] Release Lucene/Solr 5.4.1 RC2

cripts/smokeTestRelease.py > https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.4.1-RC2-rev1725212 > <https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.4.1-RC1-rev1724447/> > > The smoke tester already passed for me both with the local and remote > artifacts, so here is my +1. > -- Anshum Gupta

[jira] [Commented] (SOLR-8561) Add fallback to ZkController.getLeaderProps for a mixed 5.4-pre-5.4 deployments

[ https://issues.apache.org/jira/browse/SOLR-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104975#comment-15104975 ] Anshum Gupta commented on SOLR-8561: I read up the last couple of comments on the linked JIRA

<    5   6   7   8   9   10   11   12   13   14   >