Re: 7.0 Release Update

I will *try* to get to it, but can't confirm. If someone else has a spare cycle and can take it up before I get to it, please do. -Anshum On Tue, Jul 25, 2017 at 10:44 AM Cassandra Targett wrote: > I believe the only remaining blocker to SOLR-10803 (to mark all Trie* >

[jira] [Updated] (SOLR-11126) Node-level health check handler

[ https://issues.apache.org/jira/browse/SOLR-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-11126: Summary: Node-level health check handler (was: Top level node-level health check handler) > N

[jira] [Commented] (SOLR-6630) Deprecate the "implicit" router and rename to "manual"

[ https://issues.apache.org/jira/browse/SOLR-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099009#comment-16099009 ] Anshum Gupta commented on SOLR-6630: [~ichattopadhyaya] are you actively working on this? > Deprec

[jira] [Commented] (SOLR-10272) Use a default configset and make the configName parameter optional.

[ https://issues.apache.org/jira/browse/SOLR-10272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099005#comment-16099005 ] Anshum Gupta commented on SOLR-10272: - [~ichattopadhyaya] I think this is resolved, but can you

[jira] [Assigned] (SOLR-11131) bin/solr help doesn't mention "assert" as a COMMAND option

[ https://issues.apache.org/jira/browse/SOLR-11131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reassigned SOLR-11131: --- Assignee: Anshum Gupta (was: Erick Erickson) > bin/solr help doesn't mention &quo

[jira] [Updated] (SOLR-11131) bin/solr help doesn't mention "assert" as a COMMAND option

[ https://issues.apache.org/jira/browse/SOLR-11131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-11131: Fix Version/s: 7.1 master (8.0) > bin/solr help doesn't mention &quo

[jira] [Commented] (SOLR-11131) bin/solr help doesn't mention "assert" as a COMMAND option

[ https://issues.apache.org/jira/browse/SOLR-11131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096975#comment-16096975 ] Anshum Gupta commented on SOLR-11131: - Thanks Jason. I've committed the current version

[jira] [Commented] (SOLR-11131) bin/solr help doesn't mention "assert" as a COMMAND option

[ https://issues.apache.org/jira/browse/SOLR-11131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095018#comment-16095018 ] Anshum Gupta commented on SOLR-11131: - [~gerlowskija] can you also add this to solr.cmd

[jira] [Commented] (SOLR-11131) bin/solr help doesn't mention "assert" as a COMMAND option

[ https://issues.apache.org/jira/browse/SOLR-11131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094988#comment-16094988 ] Anshum Gupta commented on SOLR-11131: - I'll run the tests and commit this. Thanks [~gerlowskija

[jira] [Commented] (SOLR-11126) Top level node-level health check handler

[ https://issues.apache.org/jira/browse/SOLR-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16093531#comment-16093531 ] Anshum Gupta commented on SOLR-11126: - Relating to where this comes from. The original idea of having

[jira] [Created] (SOLR-11126) Top level node-level health check handler

Anshum Gupta created SOLR-11126: --- Summary: Top level node-level health check handler Key: SOLR-11126 URL: https://issues.apache.org/jira/browse/SOLR-11126 Project: Solr Issue Type: New Feature

[jira] [Resolved] (SOLR-11074) Randomize PointFields in cloud-dynamic configset and all related tests

[ https://issues.apache.org/jira/browse/SOLR-11074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-11074. - Resolution: Fixed The following tests failed when I attempted to run ant beast

[jira] [Updated] (SOLR-11074) Randomize PointFields in cloud-dynamic configset and all related tests

[ https://issues.apache.org/jira/browse/SOLR-11074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-11074: Fix Version/s: 7.1 master (8.0) > Randomize PointFields in cloud-dyna

[jira] [Commented] (SOLR-10814) Solr RuleBasedAuthorization config doesn't work seamlessly with kerberos authentication

[ https://issues.apache.org/jira/browse/SOLR-10814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090791#comment-16090791 ] Anshum Gupta commented on SOLR-10814: - I don't think I'll have the time to take a look

[jira] [Commented] (LUCENE-7901) original/default Highlighter's constructor should throw if passed null args

[ https://issues.apache.org/jira/browse/LUCENE-7901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090789#comment-16090789 ] Anshum Gupta commented on LUCENE-7901: -- [~dsmiley] sure. > original/default Highlighte

[jira] [Commented] (SOLR-11099) Provide a mechanism to add non-core level handlers

[ https://issues.apache.org/jira/browse/SOLR-11099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090722#comment-16090722 ] Anshum Gupta commented on SOLR-11099: - I did think about adding syntactic sugar on the {{.system

[jira] [Created] (SOLR-11099) Provide a mechanism to add non-core level handlers

Anshum Gupta created SOLR-11099: --- Summary: Provide a mechanism to add non-core level handlers Key: SOLR-11099 URL: https://issues.apache.org/jira/browse/SOLR-11099 Project: Solr Issue Type

[jira] [Created] (SOLR-11074) Randomize PointFields in cloud-dynamic configset and all related tests

Anshum Gupta created SOLR-11074: --- Summary: Randomize PointFields in cloud-dynamic configset and all related tests Key: SOLR-11074 URL: https://issues.apache.org/jira/browse/SOLR-11074 Project: Solr

[jira] [Commented] (SOLR-11068) Make parameter names consistent between MOVEREPLICA and REPLACENODE API

[ https://issues.apache.org/jira/browse/SOLR-11068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085957#comment-16085957 ] Anshum Gupta commented on SOLR-11068: - [~shalinmangar] sure, let's deprecate this in 7.0. > M

[jira] [Resolved] (SOLR-11060) Randomize PointFields in schema-custom-field.xml and all related tests

[ https://issues.apache.org/jira/browse/SOLR-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-11060. - Resolution: Fixed > Randomize PointFields in schema-custom-field.xml and all related te

[jira] [Updated] (SOLR-11060) Randomize PointFields in schema-custom-field.xml and all related tests

[ https://issues.apache.org/jira/browse/SOLR-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-11060: Fix Version/s: 7.1 master (8.0) > Randomize PointFields in schema-cus

[jira] [Created] (SOLR-11060) Randomize PointFields in schema-custom-field.xml and all related tests

Anshum Gupta created SOLR-11060: --- Summary: Randomize PointFields in schema-custom-field.xml and all related tests Key: SOLR-11060 URL: https://issues.apache.org/jira/browse/SOLR-11060 Project: Solr

[jira] [Updated] (SOLR-11059) Randomize PointFields in schema-blockjoinfacetcomponent.xml and all related tests

[ https://issues.apache.org/jira/browse/SOLR-11059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-11059: Fix Version/s: 7.1 master (8.0) > Randomize PointFields in sch

[jira] [Resolved] (SOLR-11059) Randomize PointFields in schema-blockjoinfacetcomponent.xml and all related tests

[ https://issues.apache.org/jira/browse/SOLR-11059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-11059. - Resolution: Fixed > Randomize PointFields in schema-blockjoinfacetcomponent.xml and all rela

[jira] [Created] (SOLR-11059) Randomize PointFields in schema-blockjoinfacetcomponent.xml and all related tests

Anshum Gupta created SOLR-11059: --- Summary: Randomize PointFields in schema-blockjoinfacetcomponent.xml and all related tests Key: SOLR-11059 URL: https://issues.apache.org/jira/browse/SOLR-11059

[jira] [Resolved] (SOLR-11048) Randomize PointFields in schema-add-schema-fields-update-processor.xml in core/src/test-files/solr/collection1

[ https://issues.apache.org/jira/browse/SOLR-11048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-11048. - Resolution: Fixed Fix Version/s: 7.1 master (8.0) > Random

[jira] [Updated] (SOLR-11048) Randomize PointFields in schema-add-schema-fields-update-processor.xml in core/src/test-files/solr/collection1

[ https://issues.apache.org/jira/browse/SOLR-11048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-11048: Summary: Randomize PointFields in schema-add-schema-fields-update-processor.xml in core/src/test

[jira] [Created] (SOLR-11048) Randomize PointFields in all server tests unless explicit reason not to

Anshum Gupta created SOLR-11048: --- Summary: Randomize PointFields in all server tests unless explicit reason not to Key: SOLR-11048 URL: https://issues.apache.org/jira/browse/SOLR-11048 Project: Solr

[jira] [Updated] (SOLR-11048) Randomize PointFields in all server tests unless explicit reason not to

[ https://issues.apache.org/jira/browse/SOLR-11048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-11048: Reporter: Anshum Gupta (was: Hoss Man) > Randomize PointFields in all server tests unless expli

[jira] [Assigned] (SOLR-11048) Randomize PointFields in all server tests unless explicit reason not to

[ https://issues.apache.org/jira/browse/SOLR-11048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reassigned SOLR-11048: --- Assignee: Anshum Gupta (was: Hoss Man) > Randomize PointFields in all server tests unl

Re: 7.0 Release Update

the 7.0 release until > that's done, it's more than just updating the example schemas if we > want to ensure a quality app for users. We still need to fix the tests > and also fix bugs that are going to be really painful for users. And > to get all that done soon, we definitely need so

Re: 7.0 Release Update

, let everyone else know. -Anshum > On Jul 10, 2017, at 8:50 AM, Cassandra Targett <casstarg...@gmail.com> wrote: > > Thanks Steve. > > On Mon, Jul 10, 2017 at 10:35 AM, Anshum Gupta <ans...@anshumgupta.net> wrote: >> Thanks Steve, and Cassandra. >> >&g

Re: Fix versions

and/or perhaps the earliest known/believed. > > On Mon, Jul 10, 2017 at 1:58 PM Anshum Gupta <ansh...@apple.com > <mailto:ansh...@apple.com>> wrote: > As long as all of us agree, and try to use the same system, I think we'll be > fine. > > I think there's a reas

[jira] [Commented] (SOLR-10887) Add .xml extension to managed-schema

[ https://issues.apache.org/jira/browse/SOLR-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080742#comment-16080742 ] Anshum Gupta commented on SOLR-10887: - [~ichattopadhyaya] , I don't see this as a blocker for 7.0. Let

Re: Fix versions

As long as all of us agree, and try to use the same system, I think we'll be fine. I think there's a reasonable consensus on the following understanding of "fixVersion/s", and "Affected Versions" - fixVersion: All branches that the code was committed. Example, assuming that the last released

Re: 7.0 Release Update

Thanks Steve, and Cassandra. On Mon, Jul 10, 2017 at 8:29 AM Steve Rowe wrote: > > > On Jul 10, 2017, at 11:04 AM, Cassandra Targett > wrote: > > > > We also need Solr Ref Guide Jenkins jobs for 7.x and 7.0 - Steve Rowe > > maybe you could help with

[jira] [Commented] (SOLR-10452) setQueryParams should be deprecated in favor of SolrClientBuilder methods

[ https://issues.apache.org/jira/browse/SOLR-10452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080462#comment-16080462 ] Anshum Gupta commented on SOLR-10452: - [~gerlowskija] I just glanced through it and don't think we

Re: Fix versions

Thanks for the insight hoss :). I agree that I went into this with my assumptions. > A user who sees that a bug is fixed in "6.6.1" has no way to be > confident that the same bug is fixed in "7.0" just because the major > number is greater -- because we might releast 6.6.1 after 7.0 is

Re: Fix versions

not required to have > changes to this page (and some selected others) be auto-copied to the dev > list somehow, e.g. by having a special account, but not required. > > On Wed, Jul 5, 2017 at 5:56 PM Anshum Gupta <ansh...@apple.com > <mailto:ansh...@apple.com>> wro

Re: Fix versions

n something project-specific. I've expressed my >> opinion on that previous post, but I'm open to any strategy. >> >> Dawid >> >> On Wed, Jul 5, 2017 at 10:42 PM, Anshum Gupta <ansh...@apple.com> wrote: >>> Hi, >>> >>> I was a

[jira] [Resolved] (SOLR-11004) Consolidate SolrClient Builder code in abstract parent class

[ https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-11004. - Resolution: Fixed > Consolidate SolrClient Builder code in abstract parent cl

[jira] [Updated] (SOLR-11004) Consolidate SolrClient Builder code in abstract parent class

[ https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-11004: Fix Version/s: (was: master (8.0)) > Consolidate SolrClient Builder code in abstract par

Fix versions

Hi, I was a bit confused in terms of setting the ‘fix version’ for JIRAs that are being committed right now. I think it makes sense for the fixVersion to just be 7.0, and nothing else for everything that is going into branch_7_0, instead of being both 7.0, and master (8.0). Any thoughts?

[jira] [Updated] (SOLR-11004) Consolidate SolrClient Builder code in abstract parent class

[ https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-11004: Fix Version/s: 7.0 > Consolidate SolrClient Builder code in abstract parent cl

[jira] [Updated] (SOLR-11004) Consolidate SolrClient Builder code in abstract parent class

[ https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-11004: Affects Version/s: (was: master (8.0)) > Consolidate SolrClient Builder code in abstract par

[jira] [Assigned] (SOLR-11004) Consolidate SolrClient Builder code in abstract parent class

[ https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reassigned SOLR-11004: --- Assignee: Anshum Gupta > Consolidate SolrClient Builder code in abstract parent cl

[jira] [Updated] (SOLR-11004) Consolidate SolrClient Builder code in abstract parent class

[ https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-11004: Attachment: SOLR-11004.patch Updated patch > Consolidate SolrClient Builder code in abstr

[jira] [Commented] (SOLR-11004) Consolidate SolrClient Builder code in abstract parent class

[ https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075172#comment-16075172 ] Anshum Gupta commented on SOLR-11004: - Thanks Jason, I've changed this a bit to remove

Re: Feature freeze @ 7.0 branch

t;> <https://issues.apache.org/jira/browse/LUCENE-7899> for 7.0; it's a simple >> rename, which I think we should do on major release. I'll get a patch up >> shortly. >> >> Thanks, >> >> Mike McCandless >> >> http://blog.mikemccan

Re: Feature freeze @ 7.0 branch

zej Białecki > <andrzej.biale...@lucidworks.com <mailto:andrzej.biale...@lucidworks.com>> > wrote: > SOLR-10878 and SOLR-10879 didn’t make it before the branches were cut, but I > think they should be included in 7x and 7_0 - I’m going to cherry-pick the > commits

[jira] [Comment Edited] (SOLR-9526) data_driven configs defaults to "strings" for unmapped fields, makes most fields containing "textual content" unsearchable, breaks tutorial examples

[ https://issues.apache.org/jira/browse/SOLR-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074877#comment-16074877 ] Anshum Gupta edited comment on SOLR-9526 at 7/5/17 2:51 PM: I think we can get

[jira] [Commented] (SOLR-9526) data_driven configs defaults to "strings" for unmapped fields, makes most fields containing "textual content" unsearchable, breaks tutorial examples

[ https://issues.apache.org/jira/browse/SOLR-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074877#comment-16074877 ] Anshum Gupta commented on SOLR-9526: I think > data_driven configs defaults to "strings"

Re: Feature freeze @ 7.0 branch

on major release. I'll get a patch up >> shortly. >> >> Thanks, >> >> Mike McCandless >> >> http://blog.mikemccandless.com >> >> On Tue, Jul 4, 2017 at 12:40 PM, Anshum Gupta <ans...@anshumgupta.net> >> wrote: >>

Re: [JENKINS] Lucene-Solr-SmokeRelease-7.x - Build # 1 - Failure

I guess we need to bump the version here to 7.1 as we have a 7.0 branch out. On Tue, Jul 4, 2017 at 9:57 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-7.x/1/ > > No tests ran. > > Build Log: > [...truncated 25711

Re: Feature freeze @ 7.0 branch

cherry-pick > the commits from master. > > On 3 Jul 2017, at 22:29, Anshum Gupta <ansh...@apple.com> wrote: > > Hi, > > I just wanted to call it out and remove any confusions around the fact > that we shouldn’t we committing ‘new features’ to branch_7_0. As far as >

[jira] [Resolved] (SOLR-10456) timeout-related setters should be deprecated in favor of SolrClientBuilder methods

[ https://issues.apache.org/jira/browse/SOLR-10456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-10456. - Resolution: Fixed Thanks Jason. > timeout-related setters should be deprecated in fa

[jira] [Commented] (SOLR-10456) timeout-related setters should be deprecated in favor of SolrClientBuilder methods

[ https://issues.apache.org/jira/browse/SOLR-10456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073160#comment-16073160 ] Anshum Gupta commented on SOLR-10456: - I plan on pushing it to branch_7_0 too as this is a deprecation

[jira] [Commented] (SOLR-10456) timeout-related setters should be deprecated in favor of SolrClientBuilder methods

[ https://issues.apache.org/jira/browse/SOLR-10456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072978#comment-16072978 ] Anshum Gupta commented on SOLR-10456: - bq. I named it generically so that it could possibly

[jira] [Commented] (SOLR-10456) timeout-related setters should be deprecated in favor of SolrClientBuilder methods

[ https://issues.apache.org/jira/browse/SOLR-10456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072969#comment-16072969 ] Anshum Gupta commented on SOLR-10456: - Thanks [~gerlowskija]. In the following code, guess we should

[jira] [Commented] (SOLR-10456) timeout-related setters should be deprecated in favor of SolrClientBuilder methods

[ https://issues.apache.org/jira/browse/SOLR-10456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072958#comment-16072958 ] Anshum Gupta commented on SOLR-10456: - I'll take a look and commit > timeout-related setters sho

[jira] [Assigned] (SOLR-10456) timeout-related setters should be deprecated in favor of SolrClientBuilder methods

[ https://issues.apache.org/jira/browse/SOLR-10456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reassigned SOLR-10456: --- Assignee: Anshum Gupta > timeout-related setters should be deprecated in fa

Re: 7.0 Release Update

Thanks Uwe! Can you clarify if Jenkins = Policeman / Apache or both ? On Mon, Jul 3, 2017 at 3:03 PM Uwe Schindler <u...@thetaphi.de> wrote: > Thanks Anshum, > > I will setup the Jenkins jobs tomorrow! > > Uwe > > > Am 3. Juli 2017 21:22:46 MESZ schrieb A

Re: /v2 API -- will there ever be a /v3?

Also, if someone has the time to take this up, can you please create a JIRA and mark is a usability blocker for 7.0 release ? -Anshum On Mon, Jul 3, 2017 at 1:55 PM Anshum Gupta <ans...@anshumgupta.net> wrote: > +1 to not having v2. I don't have a personal preference between the >

Re: /v2 API -- will there ever be a /v3?

+1 to not having v2. I don't have a personal preference between the suggestions by Shawn, and Jan, so like David, either of them would be great. -Anshum On Fri, Jun 16, 2017 at 6:59 AM Jan Høydahl wrote: > Hi, > > Now that we’re getting used to thinking

Feature freeze @ 7.0 branch

Hi, I just wanted to call it out and remove any confusions around the fact that we shouldn’t we committing ‘new features’ to branch_7_0. As far as whatever was already agreed upon in previous communications, let’s get that stuff in if it’s ready or almost there. For everything else, kindly

7.0 Release Update

The following branches have been created off master, prior to bumping up of the version: * branch_7x * branch_7_0 The versioon on master has been bumped to 8, and all tests pass. Thanks to everyone (specially Adrien, and Uwe) :) for helping out with the back-compat stuff and being patient.

Re: 7x, and 7.0 branches

Grand <jpou...@gmail.com> wrote: > Thanks Anshum, I'll have a look today. > > Le ven. 30 juin 2017 à 20:23, Anshum Gupta <ansh...@apple.com> a écrit : > >> Hi Uwe/Adrien, >> >> I reverted a bunch of changes to only get rid of the 5x format codec >> names

[jira] [Commented] (SOLR-10032) Create report to assess Solr test quality at a commit point.

[ https://issues.apache.org/jira/browse/SOLR-10032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070530#comment-16070530 ] Anshum Gupta commented on SOLR-10032: - This is looking really good! > Create report to assess S

Re: 7x, and 7.0 branches

> So backwards codec must keep all stuff in metainf and as classes that the 7.0 > original index format requires. Maybe create a dummy 7.0 index in branch-7x > to have a list of codecs to test. > > Uwe > > Am 30. Juni 2017 00:43:06 MESZ schrieb Anshum Gupta <ansh...@a

Re: 7x, and 7.0 branches

bunch of tests that use the old indexes. -Anshum > On Jun 29, 2017, at 3:10 PM, Anshum Gupta <ansh...@apple.com> wrote: > > I did remove the declaration in META-INT/services, atleast everything that > had a version in it’s name i.e. 5x, or 6x. > > I’ve also renamed th

Re: 7x, and 7.0 branches

he testIllegalCreatedVersion test, > I'd just replace 8 with 9 or Version.CURRENT.major + 1. > > We'd need to remove the compatibility layer in similarities but it can be > done as a follow-up. > > Thanks for taking care of this! > > Le jeu. 29 juin 2017 à 23:12, Anshum Gupta &l

Re: 7x, and 7.0 branches

com/anshumg/lucene-solr> P.S: I thought it’d make more sense to do this on a feature-branch but the upgrade script wasn’t happy about that. -Anshum > On Jun 29, 2017, at 9:20 AM, Anshum Gupta <ansh...@apple.com> wrote: > > Going with your suggestions, seems like w

Re: 7x, and 7.0 branches

Going with your suggestions, seems like we’d be wiping out all of the backward-codecs folder/package, is that correct ? Also, do we need to put in anything to ensure back-combat between 6x, and 7x? -Anshum > On Jun 29, 2017, at 7:21 AM, Anshum Gupta <ansh...@apple.com> wrote: &g

Re: 7x, and 7.0 branches

ard-codecs module since they are only > about 6.x codecs. > > Le mer. 28 juin 2017 à 09:57, Anshum Gupta <ansh...@apple.com > <mailto:ansh...@apple.com>> a écrit : > Thanks for confirming that Alan, I had similar thoughts but wasn’t sure. > > I don’t want t

Re: Release planning for 7.0

ming soon, so we should really have > support because the speed improvements are a main reason to move to Java 9 > with your Solr servers. > > > > Uwe > > > > - > > Uwe Schindler > > Achterdiek 19, D-28357 Bremen > > http://www.thetaphi.de > > eMail:

Re: Release planning for 7.0

- > > Uwe Schindler > > Achterdiek 19, D-28357 Bremen > > http://www.thetaphi.de > > eMail: u...@thetaphi.de > > > > *From:* Anshum Gupta [mailto:ans...@anshumgupta.net] > *Sent:* Sunday, June 25, 2017 7:52 PM > > > *To:* dev@lucene.apache.org > *Subjec

Re: 7x, and 7.0 branches

k? > > >> On 28 Jun 2017, at 08:38, Anshum Gupta <ansh...@apple.com >> <mailto:ansh...@apple.com>> wrote: >> >> I tried to move forward to see this work before automatically computing the >> versions but I have about 30 odd failing test. I’ve made tho

Re: 7x, and 7.0 branches

Version.LATEST.major+1. > > I can do those changes on Thursday if you don't feel comfortable doing them. > > > > Le mar. 27 juin 2017 à 08:12, Anshum Gupta <ansh...@apple.com > <mailto:ansh...@apple.com>> a écrit : > Without making any changes at all and just bum

Re: Release planning for 7.0

Erick, sure. If you think it'd take longer, could you mark that as a blocker so I hold back moving ahead with the release process? -Anshum On Mon, Jun 26, 2017 at 11:28 PM Anshum Gupta <ans...@anshumgupta.net> wrote: > Hi Alan, > > Sorry for the delay in replying but go a

Re: Release planning for 7.0

until at > least the branch for 6.7 is cur for the purpose of easy back-compat > management and guarantee. > > Also, sorry for being on radio silence for the last few days. I’d been > traveling but now I’m back :). > > -Anshum Gupta > > On Sun, Jun 18, 2017 at 8:57 A

Re: 7x, and 7.0 branches

> 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 <ans...@anshumgupta.net > <mailto:ans...@anshumgupta.net>> wrote: > Thanks Adrien, sadly, the tests aren'

[jira] [Resolved] (SOLR-9535) SolrClients should have protected constructors

[ https://issues.apache.org/jira/browse/SOLR-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-9535. Resolution: Fixed > SolrClients should have protected construct

Re: 7x, and 7.0 branches

s whether other changes > are required, I'm currently traveling but can look when I'm back on > Thursday. Feel free to push the branches if tests are passing, we can fix > things later? > > Le lun. 26 juin 2017 à 07:13, Anshum Gupta <ans...@anshumgupta.net> a > écrit : > >&

Re: 7x, and 7.0 branches

n, Jun 25, 2017 at 9:45 PM Anshum Gupta <ans...@anshumgupta.net> wrote: > Hi, > > I am working on creating the 7x, and 7.0 branches but I have the following > failing tests: >[junit4] Tests with failures [seed: 4FBDDCD3F96316D3]: >[junit4] - > org.apache.lucene

7x, and 7.0 branches

Hi, I am working on creating the 7x, and 7.0 branches but I have the following failing tests: [junit4] Tests with failures [seed: 4FBDDCD3F96316D3]: [junit4] - org.apache.lucene.index.TestSegmentInfos.testVersionsTwoSegments [junit4] -

Re: Release planning for 7.0

Miller. If the hadoop people have a simple bugfix release for the earlier > version, we may also be able to fix branch_6x and branch_6_6 (but I > disabled them on Jenkins anyways). > > > > Uwe > > > > - > > Uwe Schindler > > Achterdiek 19, D-28357 Bremen &g

Re: Release planning for 7.0

eels to me like the kind of change that > should only be made in a major release due to back-compat concerns. > > If this can make it in after the branch is created, then no problem, but > otherwise it might be worth waiting another day before branching. Up to you. > > -Trey > &g

Re: Release planning for 7.0

g the branch, as well as > once the branch is in place. > I'm right now on travel, and unable to finish SOLR-10574 until Monday > (possibly Tuesday). > Regards, > Ishan > > On Tue, Jun 20, 2017 at 5:08 PM, Anshum Gupta <ans...@anshumgupta.net> > wrote: > >>

[jira] [Resolved] (SOLR-10915) Make SolrClient classes extendable without code duplication

[ https://issues.apache.org/jira/browse/SOLR-10915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-10915. - Resolution: Fixed > Make SolrClient classes extendable without code duplicat

[jira] [Commented] (SOLR-10915) Make SolrClient classes extendable without code duplication

[ https://issues.apache.org/jira/browse/SOLR-10915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062058#comment-16062058 ] Anshum Gupta commented on SOLR-10915: - [~mkhludnev] did you intend to comment on this JIRA? On a side

[jira] [Commented] (SOLR-10915) Make SolrClient classes extendable without code duplication

[ https://issues.apache.org/jira/browse/SOLR-10915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061165#comment-16061165 ] Anshum Gupta commented on SOLR-10915: - I'm seeing some pre-commit failures. I've fixed a couple

[jira] [Updated] (SOLR-10915) Make SolrClient classes extendable without code duplication

[ https://issues.apache.org/jira/browse/SOLR-10915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-10915: Attachment: SOLR-10915.patch Thanks Jason. Patch looks good. I've fixed a typo here

[jira] [Commented] (SOLR-10915) Make SolrClient classes extendable without code duplication

[ https://issues.apache.org/jira/browse/SOLR-10915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056564#comment-16056564 ] Anshum Gupta commented on SOLR-10915: - There's existing constructors that were released in 6.6, which

[jira] [Commented] (SOLR-10915) Make SolrClient classes extendable without code duplication

[ https://issues.apache.org/jira/browse/SOLR-10915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056496#comment-16056496 ] Anshum Gupta commented on SOLR-10915: - [~gerlowskija] one more thing, can you have the extension

[jira] [Commented] (SOLR-10915) Make SolrClient classes extendable without code duplication

[ https://issues.apache.org/jira/browse/SOLR-10915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056210#comment-16056210 ] Anshum Gupta commented on SOLR-10915: - Sorry about that confusion, should've read what I wrote :). I

[jira] [Commented] (SOLR-10915) Make SolrClient classes extendable without code duplication

[ https://issues.apache.org/jira/browse/SOLR-10915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056177#comment-16056177 ] Anshum Gupta commented on SOLR-10915: - Thanks Jason. The patch looks good overall but I think we

Re: Release planning for 7.0

ues.apache.org/jira/browse/LUCENE-7877 in > for 7.0 > > - should be able to commit in the next couple of days. > > > > Alan Woodward > > www.flax.co.uk > > > > > > On 19 Jun 2017, at 15:45, Anshum Gupta <ans...@anshumgupta.net> wrote: > > >

[jira] [Updated] (LUCENE-7877) Replace PrefixAwareTokenStream

[ https://issues.apache.org/jira/browse/LUCENE-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated LUCENE-7877: - Fix Version/s: master (7.0) > Replace PrefixAwareTokenStr

[jira] [Updated] (SOLR-5958) Document (and fix) numShards and router selection parameter in SolrCloud

[ https://issues.apache.org/jira/browse/SOLR-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5958: --- Issue Type: Improvement (was: Task) > Document (and fix) numShards and router selection parame

[jira] [Commented] (SOLR-5958) Document (and fix) numShards and router selection parameter in SolrCloud

[ https://issues.apache.org/jira/browse/SOLR-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054839#comment-16054839 ] Anshum Gupta commented on SOLR-5958: Coming back to this after a really long time. It's a low hanging

<    1   2   3   4   5   6   7   8   9   10   >