[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Cassandra Targett (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15960860#comment-15960860
 ] 

Cassandra Targett commented on SOLR-8029:
-

[~noble.paul] - Since the new APIs were included with Solr 6.5, and there is 
SOLR-10432 for follow-on items, this should be resolved, right?

> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867081#comment-15867081
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 2470fbaa0ee4d1a211957bc47242bd081a31234d in lucene-solr's branch 
refs/heads/master from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=2470fba ]

SOLR-8029: introspect was not showing for certain collection apis


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867078#comment-15867078
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 9a1702a8f5b5496893a99c4e1f39cd58520786ae in lucene-solr's branch 
refs/heads/master from [~ichattopadhyaya]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9a1702a ]

SOLR-8029: Reverting the previous commit and the merge


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866993#comment-15866993
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 65c6c576b720b19029a10bf14f81d4de23302863 in lucene-solr's branch 
refs/heads/master from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=65c6c57 ]

SOLR-8029: introspect was not showing for certain collection apis


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866988#comment-15866988
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 5c4ee10683fab338f3f4619a850d509c716ebe33 in lucene-solr's branch 
refs/heads/branch_6x from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5c4ee10 ]

SOLR-8029: introspect was not showing for certain collection apis


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863865#comment-15863865
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 8b5dec52f5d331ad3febd599016f8dd85480e628 in lucene-solr's branch 
refs/heads/branch_6x from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8b5dec5 ]

SOLR-8029: disabled easymock for java9


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863825#comment-15863825
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 563f522643b5460e5b3bde1815f3f0b08c248eef in lucene-solr's branch 
refs/heads/master from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=563f522 ]

SOLR-8029: disabled easymock for java9


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Noble Paul (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15858019#comment-15858019
 ] 

Noble Paul commented on SOLR-8029:
--

sure [~romseygeek] . I'll fix it

> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Alan Woodward (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855624#comment-15855624
 ] 

Alan Woodward commented on SOLR-8029:
-

Hey [~noble.paul], this is failing on the Java 9 Jenkins runs because 
TestCoreAdminApis uses EasyMock (see SOLR-9893 and SOLR-9966).  You need to use 
Mockito instead.

> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852921#comment-15852921
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit d72634813b2e9014b70ce753a02c8d7297af8c81 in lucene-solr's branch 
refs/heads/branch_6x from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d726348 ]

SOLR-8029: Added new style APIs and a framework for creating new APIs and 
mapping old APIs to new


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Noble Paul (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848297#comment-15848297
 ] 

Noble Paul commented on SOLR-8029:
--

Things looks stable and I plan to port it to branch_6x. Any inputs, feedback 
are welcome. Especially on the framework, configuration etc. If there are 
missing APIs we can open a ticket and fix them seperately

> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Re: [jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Yago Riveiro]

No command to list aliases?

Call CLUSTERSTATUS to fetch the available list of alias is annoying, aliases 
belongs to collections not to the CLUSTER.

--

/Yago Riveiro

On 27 Jan 2017 23:01 +, Noble Paul (JIRA) , wrote:
>
> [ 
> https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843618#comment-15843618
>  ]
>
> Noble Paul commented on SOLR-8029:
> --
>
> Refer to this document. This is not fully updated and some of the items 
> marked as "missing" are actually implemented.
> https://docs.google.com/document/d/18n9IL6y82C8gnBred6lzG0GLaT3OsZZsBvJQ2YAt72I/edit?usp=sharing
>
> > Modernize and standardize Solr APIs
> > ---
> >
> > Key: SOLR-8029
> > URL: https://issues.apache.org/jira/browse/SOLR-8029
> > Project: Solr
> > Issue Type: Improvement
> > Affects Versions: 6.0
> > Reporter: Noble Paul
> > Assignee: Noble Paul
> > Labels: API, EaseOfUse
> > Fix For: 6.0
> >
> > Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> > SOLR-8029.patch, SOLR-8029.patch
> >
> >
> > Solr APIs have organically evolved and they are sometimes inconsistent with 
> > each other or not in sync with the widely followed conventions of HTTP 
> > protocol. Trying to make incremental changes to make them modern is like 
> > applying band-aid. So, we have done a complete rethink of what the APIs 
> > should be. The most notable aspects of the API are as follows:
> > The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> > APIs will continue to work under the {{/solr}} path as they used to and 
> > they will be eventually deprecated.
> > There are 4 types of requests in the new API
> > * {{/v2//*}} : Hit a collection directly or manage 
> > collections/shards/replicas
> > * {{/v2//*}} : Hit a core directly or manage cores
> > * {{/v2/cluster/*}} : Operations on cluster not pertaining to any 
> > collection or core. e.g: security, overseer ops etc
> > This will be released as part of a major release. Check the link given 
> > below for the full specification. Your comments are welcome
> > [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Noble Paul (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843618#comment-15843618
 ] 

Noble Paul commented on SOLR-8029:
--

Refer to this document. This is not fully updated and some of the items marked 
as "missing" are actually implemented. 
https://docs.google.com/document/d/18n9IL6y82C8gnBred6lzG0GLaT3OsZZsBvJQ2YAt72I/edit?usp=sharing

> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Noble Paul (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843526#comment-15843526
 ] 

Noble Paul commented on SOLR-8029:
--

[~arafalov] Good question. 

It's unlikely that it sticks to the original documentation fully.

I shall just put up a small one pager for folks who wish to review this quickly 

> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Alexandre Rafalovitch (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843499#comment-15843499
 ] 

Alexandre Rafalovitch commented on SOLR-8029:
-

Awesome news.

So, is this now fully implementing original specs and answering all issue 
questions? Or is there a newer document reflecting the actual implementation. 

How do we review this, apart from pure code-reading?

> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch, SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838966#comment-15838966
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 5a8dfd96a28bc316d74b5b7e74b28f16b5bd3f4b in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5a8dfd9 ]

SOLR-8029: fixing precommit errors


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[David Smiley (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838668#comment-15838668
 ] 

David Smiley commented on SOLR-8029:


Exciting indeed :-)  Congrats Noble & everyone else for working so hard on it.

> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Ishan Chattopadhyaya (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838401#comment-15838401
 ] 

Ishan Chattopadhyaya commented on SOLR-8029:


bq. I'm planning to commit this to master shortly
+1. Yay, this is exciting!

> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Noble Paul (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838373#comment-15838373
 ] 

Noble Paul commented on SOLR-8029:
--

I'm planning to commit this to master shortly

> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838370#comment-15838370
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit c91b96211b9e88c6cc7a4e3aedc14e4f1375dab8 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c91b962 ]

SOLR-8029: fixing some test errors


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838369#comment-15838369
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 4ddaba397d30f9b5344545d08c809488633638d1 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4ddaba3 ]

SOLR-8029: fixing some test errors


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827123#comment-15827123
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

postmas...@opentext.net
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.







Diagnostic information for administrators:

Generating server: opentext.net

postmas...@opentext.net
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Original message headers:

Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by
 otwlxg10.opentext.net (10.2.103.151) with Microsoft SMTP Server id
 14.3.319.2; Tue, 17 Jan 2017 19:14:38 -0500
Received: from mx0a-00102601.pphosted.com (mx0b-00102601.pphosted.com
 [67.231.152.222])  by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I0EcLY008769  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for ; Tue, 17 Jan 2017 19:14:38 -0500
Received: from pps.filterd (m0001253.ppops.net [127.0.0.1]) by
 mx0b-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I0BWMa025586
for ; Tue, 17 Jan 2017 19:14:38 -0500
Received: from spamd4-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0b-00102601.pphosted.com with ESMTP id 27ydm4wn0e-1
for ; Tue, 17 Jan 2017 19:14:37 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd4-us-west.apache.org
 (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 0611FC12C0
for
 ; Wed, 18 Jan 2017 00:14:37 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])   by localhost
 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with 
ESMTP
 id r8pOFYnXPoU5 for ; Wed, 18 Jan 2017 00:14:33
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-us.apache.org (ASF Mail Server at
 mx1-lw-us.apache.org) with ESMTP id EFEE25FC2B for ;
 Wed, 18 Jan 2017 00:14:31 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id 5FD41E736Cfor
 ; Wed, 18 Jan 2017 00:14:29 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id A0022252A9  for ; Wed, 18 Jan 2017 00:14:27 +
 (UTC)
Date: Wed, 18 Jan 2017 00:14:27 +
From: "Steve Rowe (JIRA)" 
To: 
Message-ID: 
In-Reply-To: 
References:  

Subject: [jira] [Issue Comment Deleted] (SOLR-8029) Modernize and
 standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGBgaEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGBoacRMSEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThdnf2Z8cnJtdUxERxldfUxkemUYXU 
FhH0Z8X1hJR15hfREKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsbGgQeEgQSHBAbHhofGhEKXlkXe
 l5sTWMRCk1cFxkbHBEKTFoXaGlNTV0RCkxGF2xraxEKQ1oXGBoTBBsSEgQbHgQbHhgRCkJeFxsR 
CkJGF2ZEWXtIcnlAckxMEQpCRRdvBWBmWV1oQEsfRhEKQk4XYUBCE0NTa0VmUkYRCkJMF2wFRn4 
dHBh9Tm9IEQpCbBdpbkhMe0lpWk5+ThEKQkAXbh8aRWFyTEFaWGkRCkJYF3pkcktnex56fWVzEQ
 paWBcZEQpwZxd6e1IaZGtIfE5MYRAaEQpwaBdpUG8fWXJbXnxmbxAaEQpwaBdicHhjeFJPQ14aY 
BAaEQpwaBdnZh57Zx4Fc0MFXxAaEQpwaBdrbRNBbVtfHXNdRRAaEQpwaBduZURQQBlJSB5YWxAa 
EQpwfxdpHl57YGV5Q2JIBRAbGRwRCnBfF2B7aRpLSFBhGE55EBwaEQpwfRdjWUxffR9iE2R4WxA
 aEQpwZxdgc05kARhZHFxlHhAaEQpwZxdlWH4SE0deZ1BGfRAaEQpwfRdmbm9OfG59QUBGTRAeEh 
EKcH8Xent/HG5fUnN+E0UQHh8RCnBfF2FvG1lJGUV5eW8fEB4SEQpwfRdkZGxfW3J4c0tsQRAeE 
hEKcGwXZ2FHbWtIQhJieWgQGhEKcEMXY15zE2cBRmx6UGwQHRoRCm1+FxoRClhNF0sRIA==
Content-Transfer-Encoding: Quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, 
definitions=2017-01-17_17:,,
 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=0 
malwarescore=0
 suspectscore=1 phishscore=0 

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827122#comment-15827122
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

postmas...@opentext.net
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.







Diagnostic information for administrators:

Generating server: opentext.net

postmas...@opentext.net
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Original message headers:

Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by
 otwlxg10.opentext.net (10.2.103.151) with Microsoft SMTP Server id
 14.3.319.2; Tue, 17 Jan 2017 19:14:41 -0500
Received: from mx0a-00102601.pphosted.com (mx0b-00102601.pphosted.com
 [67.231.152.222])  by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I0Efde008794  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for ; Tue, 17 Jan 2017 19:14:41 -0500
Received: from pps.filterd (m0001253.ppops.net [127.0.0.1]) by
 mx0b-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I0BTLE025583
for ; Tue, 17 Jan 2017 19:14:40 -0500
Received: from spamd4-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0b-00102601.pphosted.com with ESMTP id 27ydm4wn0h-1
for ; Tue, 17 Jan 2017 19:14:40 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd4-us-west.apache.org
 (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 443BEC0E36
for
 ; Wed, 18 Jan 2017 00:14:40 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-eu.apache.org ([10.40.0.8])   by localhost
 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with 
ESMTP
 id gyc1tkE1Q_wq for ; Wed, 18 Jan 2017 00:14:37
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-eu.apache.org (ASF Mail Server at
 mx1-lw-eu.apache.org) with ESMTP id 117A35FDFB for ;
 Wed, 18 Jan 2017 00:14:36 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id 8EC34EAAE5for
 ; Wed, 18 Jan 2017 00:14:30 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id D0831252B1  for ; Wed, 18 Jan 2017 00:14:28 +
 (UTC)
Date: Wed, 18 Jan 2017 00:14:28 +
From: "Steve Rowe (JIRA)" 
To: 
Message-ID: 
In-Reply-To: 
References:  

Subject: [jira] [Issue Comment Deleted] (SOLR-8029) Modernize and
 standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGBgaEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGBoacRMSEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThdcdWJpGlhweB8bR1JcZWIcEnpeRV 
MdGkBaHWcfTR9nbhEKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsbGgQeEgQSHBAbHhofGhEKXlkXe
 l5sTWYRCk1cFxsTHhEKTFoXaGlNTV0RCkxGF2xraxEKQ1oXGBoTBBsSEgQbHgQbHhgRCkJeFxsR 
CkJGF2ZEWXtIcnlAckxMEQpCRRdvBWBmWV1oQEsfRhEKQk4XYUBCE0NTa0VmUkYRCkJMF2wFRn4 
dHBh9Tm9IEQpCbBdpbkhMe0lpWk5+ThEKQkAXbh8aRWFyTEFaWGkRCkJYF3pkcktnex56fWVzEQ
 pNXhcbEQpaWBcZEQpwZxdtRlJAWn1ib34FYxAaEQpwaBd6QFwdaRNZS2wcZxAaEQpwaBdsY3pDX 
HkZcmJJXxAaEQpwaBdhHkF5GnhHHlxOcBAaEQpwaBdgG2diQkZFWxlMRBAaEQpwaBdtBV5pXm9a 
Wx9YHRAaEQpwfxdpHl57YGV5Q2JIBRAbGRwRCnBfF2B7aRpLSFBhGE55EBwaEQpwfRdjWUxffR9
 iE2R4WxAaEQpwZxd6e1IaZGtIfE5MYRAaEQpwZxdgc05kARhZHFxlHhAaEQpwZxdlWH4SE0deZ1 
BGfRAaEQpwfRdmbm9OfG59QUBGTRAeEhEKcH8Xent/HG5fUnN+E0UQHh8RCnBfF2FvG1lJGUV5e 
W8fEB4SEQpwfRdkZGxfW3J4c0tsQRAeEhEKcGwXZ2FHbWtIQhJieWgQGhEKcEMXY15zE2cBRmx6
 UGwQHRoRCm1+FxsRClhNF0sRIA==
Content-Transfer-Encoding: Quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, 
definitions=2017-01-17_17:,,
 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=0 
malwarescore=0
 

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827121#comment-15827121
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

postmas...@opentext.net
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.







Diagnostic information for administrators:

Generating server: opentext.net

postmas...@opentext.net
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Original message headers:

Received: from wldmzsvc05.dmz.opentext.com (10.2.170.16) by
 otwlxg10.opentext.net (10.2.103.151) with Microsoft SMTP Server id
 14.3.319.2; Tue, 17 Jan 2017 19:14:39 -0500
Received: from mx0a-00102601.pphosted.com (mx0b-00102601.pphosted.com
 [67.231.152.222])  by wldmzsvc05.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I0Eck8021201  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for ; Tue, 17 Jan 2017 19:14:38 -0500
Received: from pps.filterd (m0001253.ppops.net [127.0.0.1]) by
 mx0b-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I0BbY0025598
for ; Tue, 17 Jan 2017 19:14:38 -0500
Received: from spamd2-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0b-00102601.pphosted.com with ESMTP id 27ydm4wn0f-1
for ; Tue, 17 Jan 2017 19:14:38 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd2-us-west.apache.org
 (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id B24CB1A04DA   
for
 ; Wed, 18 Jan 2017 00:14:37 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])   by localhost
 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)  with 
ESMTP
 id c8Weof8c5Ytl for ; Wed, 18 Jan 2017 00:14:35
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-us.apache.org (ASF Mail Server at
 mx1-lw-us.apache.org) with ESMTP id 684DD61B34 for ;
 Wed, 18 Jan 2017 00:14:33 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id B2BB9EAAB4for
 ; Wed, 18 Jan 2017 00:14:29 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id EDFDB2528A  for ; Wed, 18 Jan 2017 00:14:27 +
 (UTC)
Date: Wed, 18 Jan 2017 00:14:27 +
From: "Steve Rowe (JIRA)" 
To: 
Message-ID: 
In-Reply-To: 
References:  

Subject: [jira] [Issue Comment Deleted] (SOLR-8029) Modernize and
 standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGBgaEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGBoacRMSEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThcYeGNsek57el9BH3IbW2xlb2JnB2 
tbGFxpQH5+SUJlfBEKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsbGgQeEgQSHBAbHhofGhEKXlkXe
 l5sTWARCk1cFxgdEhEKTFoXaGlNTV0RCkxGF2xraxEKQ1oXGBoTBBsSEgQbHgQbHhgRCkJeFxsR 
CkJGF2ZEWXtIcnlAckxMEQpCRRdvBWBmWV1oQEsfRhEKQk4XYUBCE0NTa0VmUkYRCkJMF2wFRn4 
dHBh9Tm9IEQpCbBdpbkhMe0lpWk5+ThEKQkAXbh8aRWFyTEFaWGkRCkJYF3pkcktnex56fWVzEQ
 pNXhcbEQpaWBcZEQpwZxd6e1IaZGtIfE5MYRAaEQpwaBdicHhjeFJPQ14aYBAaEQpwaBdjeWNtH 
2MZclhafxAaEQpwaBdtAWtZTHxcGBNcARAaEQpwaBdofxlTfltEWXJMUxAaEQpwaBduTn1FYh9f 
QnpeWxAaEQpwfxdpHl57YGV5Q2JIBRAbGRwRCnBfF2B7aRpLSFBhGE55EBwaEQpwfRdjWUxffR9
 iE2R4WxAaEQpwZxdgc05kARhZHFxlHhAaEQpwZxdlWH4SE0deZ1BGfRAaEQpwfRdmbm9OfG59QU 
BGTRAeEhEKcH8Xent/HG5fUnN+E0UQHh8RCnBfF2FvG1lJGUV5eW8fEB4SEQpwfRdkZGxfW3J4c 
0tsQRAeEhEKcGwXZ2FHbWtIQhJieWgQGhEKcEMXY15zE2cBRmx6UGwQHRoRCm1+FxsRClhNF0sR IA==
Content-Transfer-Encoding: Quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, 
definitions=2017-01-17_17:,,
 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=0 
malwarescore=0
 suspectscore=1 phishscore=0 

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827120#comment-15827120
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

postmas...@opentext.net
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.







Diagnostic information for administrators:

Generating server: opentext.net

postmas...@opentext.net
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Original message headers:

Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by
 otwlxg10.opentext.net (10.2.103.151) with Microsoft SMTP Server id
 14.3.319.2; Tue, 17 Jan 2017 19:14:38 -0500
Received: from mx0a-00102601.pphosted.com (mx0a-00102601.pphosted.com
 [67.231.144.228])  by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I0Eb0H008768  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for ; Tue, 17 Jan 2017 19:14:38 -0500
Received: from pps.filterd (m825.ppops.net [127.0.0.1]) by
 mx0a-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I0DVQH025087
for ; Tue, 17 Jan 2017 19:14:37 -0500
Received: from spamd1-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0a-00102601.pphosted.com with ESMTP id 27ye4gajd2-1
for ; Tue, 17 Jan 2017 19:14:37 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd1-us-west.apache.org
 (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 5143CC1792
for
 ; Wed, 18 Jan 2017 00:14:37 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-eu.apache.org ([10.40.0.8])   by localhost
 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)  with 
ESMTP
 id f-vJflENRsEW for ; Wed, 18 Jan 2017 00:14:35
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-eu.apache.org (ASF Mail Server at
 mx1-lw-eu.apache.org) with ESMTP id 9D0025FDEE for ;
 Wed, 18 Jan 2017 00:14:34 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id 28621EAACDfor
 ; Wed, 18 Jan 2017 00:14:30 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id 7A6AB25297  for ; Wed, 18 Jan 2017 00:14:28 +
 (UTC)
Date: Wed, 18 Jan 2017 00:14:28 +
From: "Steve Rowe (JIRA)" 
To: 
Message-ID: 
In-Reply-To: 
References:  

Subject: [jira] [Issue Comment Deleted] (SOLR-8029) Modernize and
 standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGx0ZEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGx8ZcRkZEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThcaYWlYTUJ5WnN4TR5penIeZnhrbh 
luGhwHUm9eEmx1YBEKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsaGgQeEgQfEBseGh8aEQpeWRd6X
 mxNYxEKTVwXGB8cEQpMWhdoaU1NXREKTEYXbGtrEQpDWhcYGhMEGxISBBseBBseGBEKQl4XGxEK 
QkYXZkRZe0hyeUByTEwRCkJFF28FYGZZXWhASx9GEQpCThdhQEITQ1NrRWZSRhEKQkwXbAVGfh0 
cGH1Ob0gRCkJsF2luSEx7SWlaTn5OEQpCQBduHxpFYXJMQVpYaREKQlgXemRyS2d7Hnp9ZXMRCk
 1eFxsRClpYFxkRCnBnF3p7Uhpka0h8TkxhEBkaEQpwaBdlRntoXW1nbAFoGxAaEQpwaBdicHhje 
FJPQ14aYBAaEQpwaBdrHR1we1tGbmJZGhAaEQpwaBdnEkFrZEYffR9dThAaEQpwaBduWEhfXE9s 
HkNjUBAaEQpwfxdpHl57YGV5Q2JIBRAbGxMRCnBfF2B7aRpLSFBhGE55EBwaEQpwfRdjWUxffR9
 iE2R4WxAaEQpwZxdgc05kARhZHFxlHhAZGhEKcGcXZVh+EhNHXmdQRn0QGRoRCnB9F2Zub058bn 
1BQEZNEB4SEQpwfxd6e38cbl9Sc34TRRAfGhEKcF8XYW8bWUkZRXl5bx8QHhIRCnB9F2RkbF9bc 
nhzS2xBEB4SEQpwbBdnYUdta0hCEmJ5aBAaEQpwQxdjXnMTZwFGbHpQbBAdGhEKbX4XGxEKWE0X SxEg
Content-Transfer-Encoding: Quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, 
definitions=2017-01-17_17:,,
 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=0 
malwarescore=0
 suspectscore=1 phishscore=0 

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827117#comment-15827117
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

postmas...@opentext.net
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.







Diagnostic information for administrators:

Generating server: opentext.net

postmas...@opentext.net
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Original message headers:

Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by
 otwlxg12.opentext.net (10.2.103.213) with Microsoft SMTP Server (TLS) id
 14.3.319.2; Tue, 17 Jan 2017 19:14:44 -0500
Received: from mx0a-00102601.pphosted.com (mx0a-00102601.pphosted.com
 [67.231.144.228])  by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I0EhBs008828  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for ; Tue, 17 Jan 2017 19:14:44 -0500
Received: from pps.filterd (m803.ppops.net [127.0.0.1]) by
 mx0a-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I0CxPP031602
for ; Tue, 17 Jan 2017 19:14:43 -0500
Received: from spamd1-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0a-00102601.pphosted.com with ESMTP id 27ygup1mb8-1
for ; Tue, 17 Jan 2017 19:14:43 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd1-us-west.apache.org
 (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E2404C1739
for
 ; Wed, 18 Jan 2017 00:14:42 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])   by localhost
 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)  with 
ESMTP
 id plCT5mAinYjs for ; Wed, 18 Jan 2017 00:14:42
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-us.apache.org (ASF Mail Server at
 mx1-lw-us.apache.org) with ESMTP id F24495FE3F for ;
 Wed, 18 Jan 2017 00:14:39 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id D3AA3E867Dfor
 ; Wed, 18 Jan 2017 00:14:28 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id 58BB825290  for ; Wed, 18 Jan 2017 00:14:27 +
 (UTC)
Date: Wed, 18 Jan 2017 00:14:27 +
From: "Steve Rowe (JIRA)" 
To: 
Message-ID: 
In-Reply-To: 
References:  

Subject: [jira] [Issue Comment Deleted] (SOLR-8029) Modernize and
 standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGx0ZEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGx8ZcRkZEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThcfekRwY0NcB1BQcElQE3xiQm4eYR 
xdbWsac3MSbR17TREKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsaGgQeEgQfEBseGh8aEQpeWRd6X
 mxNZREKTVwXHhoYEQpMWhdoaU1NXREKTEYXbGtrEQpDWhcYGhMEGxISBBseBBseGBEKQl4XGxEK 
QkYXZkRZe0hyeUByTEwRCkJFF28FYGZZXWhASx9GEQpCThdhQEITQ1NrRWZSRhEKQkwXbAVGfh0 
cGH1Ob0gRCkJsF2luSEx7SWlaTn5OEQpCQBduHxpFYXJMQVpYaREKQlgXemRyS2d7Hnp9ZXMRCl
 pYFxkRCnBnF3p7Uhpka0h8TkxhEBkaEQpwaBdiU29FSUtseB5hYhAaEQpwaBdicHhjeFJPQ14aY 
BAaEQpwaBd6GX1mekxbZGVnYhAaEQpwaBdickwZBV9uHXlpARAaEQpwaBdoXnBSEktdbHJQQBAa 
EQpwfxdpHl57YGV5Q2JIBRAbGxMRCnBfF2B7aRpLSFBhGE55EBwaEQpwfRdjWUxffR9iE2R4WxA
 aEQpwZxdgc05kARhZHFxlHhAZGhEKcGcXZVh+EhNHXmdQRn0QGRoRCnB9F2Zub058bn1BQEZNEB 
4SEQpwfxd6e38cbl9Sc34TRRAfGhEKcF8XYW8bWUkZRXl5bx8QHhIRCnB9F2RkbF9bcnhzS2xBE 
B4SEQpwbBdnYUdta0hCEmJ5aBAaEQpwQxdjXnMTZwFGbHpQbBAdGhEKbX4XGhEKWE0XSxEg
Content-Transfer-Encoding: Quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, 
definitions=2017-01-17_17:,,
 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=0 
malwarescore=0
 suspectscore=1 phishscore=0 

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827118#comment-15827118
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

postmas...@opentext.net
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.







Diagnostic information for administrators:

Generating server: opentext.net

postmas...@opentext.net
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Original message headers:

Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by
 otwlxg12.opentext.net (10.2.103.213) with Microsoft SMTP Server (TLS) id
 14.3.319.2; Tue, 17 Jan 2017 19:14:43 -0500
Received: from mx0a-00102601.pphosted.com (mx0b-00102601.pphosted.com
 [67.231.152.222])  by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I0Eh5D008823  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for ; Tue, 17 Jan 2017 19:14:43 -0500
Received: from pps.filterd (m0044805.ppops.net [127.0.0.1]) by
 mx0b-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I0BfRl024715
for ; Tue, 17 Jan 2017 19:14:43 -0500
Received: from spamd3-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0b-00102601.pphosted.com with ESMTP id 27ygp0w0gw-1
for ; Tue, 17 Jan 2017 19:14:43 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd3-us-west.apache.org
 (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 8E05B186112   
for
 ; Wed, 18 Jan 2017 00:14:42 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])   by localhost
 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with 
ESMTP
 id UMmbsdNV3kUA for ; Wed, 18 Jan 2017 00:14:40
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-us.apache.org (ASF Mail Server at
 mx1-lw-us.apache.org) with ESMTP id 4D75A5FC87 for ;
 Wed, 18 Jan 2017 00:14:37 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id EAA57EAAFFfor
 ; Wed, 18 Jan 2017 00:14:30 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id 5567725284  for ; Wed, 18 Jan 2017 00:14:29 +
 (UTC)
Date: Wed, 18 Jan 2017 00:14:29 +
From: "Steve Rowe (JIRA)" 
To: 
Message-ID: 
In-Reply-To: 
References:  

Subject: [jira] [Issue Comment Deleted] (SOLR-8029) Modernize and
 standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGBgaEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGBoacRMSEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThceQR9tehNSYHwdE1NbXENkY257U0 
98a0N4WhgHUxtjchEKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsbGgQeEgQSHBAbHhofGhEKXlkXe
 l5sTWURCk1cFxkbEhEKTFoXaGlNTV0RCkxGF2xraxEKQ1oXGBoTBBsSEgQbHgQbHhgRCkJeFxsR 
CkJGF2ZEWXtIcnlAckxMEQpCRRdvBWBmWV1oQEsfRhEKQk4XYUBCE0NTa0VmUkYRCkJMF2wFRn4 
dHBh9Tm9IEQpCbBdpbkhMe0lpWk5+ThEKQkAXbh8aRWFyTEFaWGkRCkJYF3pkcktnex56fWVzEQ
 paWBcZEQpwZxd6e1IaZGtIfE5MYRAaEQpwaBdicHhjeFJPQ14aYBAaEQpwaBdtZRlTGkJPYR9Zc 
BAaEQpwaBdoHUxeWhtOZhpOExAaEQpwaBdnQEVHGVhbXkJLYxAaEQpwaBdhf15ZTm4SRXJ7XhAa 
EQpwfxdpHl57YGV5Q2JIBRAbGRwRCnBfF2B7aRpLSFBhGE55EBwaEQpwfRdjWUxffR9iE2R4WxA
 aEQpwZxdgc05kARhZHFxlHhAaEQpwZxdlWH4SE0deZ1BGfRAaEQpwfRdmbm9OfG59QUBGTRAeEh 
EKcH8Xent/HG5fUnN+E0UQHh8RCnBfF2FvG1lJGUV5eW8fEB4SEQpwfRdkZGxfW3J4c0tsQRAeE 
hEKcGwXZ2FHbWtIQhJieWgQGhEKcEMXY15zE2cBRmx6UGwQHRoRCm1+FxoRClhNF0sRIA==
Content-Transfer-Encoding: Quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, 
definitions=2017-01-17_17:,,
 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=0 
malwarescore=0
 suspectscore=1 phishscore=0 

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827114#comment-15827114
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

postmas...@opentext.net
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.







Diagnostic information for administrators:

Generating server: opentext.net

postmas...@opentext.net
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Original message headers:

Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by
 otwlxg10.opentext.net (10.2.103.151) with Microsoft SMTP Server id
 14.3.319.2; Tue, 17 Jan 2017 19:11:54 -0500
Received: from mx0a-00102601.pphosted.com (mx0a-00102601.pphosted.com
 [67.231.144.228])  by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I0BpWu007603  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for ; Tue, 17 Jan 2017 19:11:52 -0500
Received: from pps.filterd (m803.ppops.net [127.0.0.1]) by
 mx0a-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I02GXx023608
for ; Tue, 17 Jan 2017 19:11:51 -0500
Received: from spamd3-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0a-00102601.pphosted.com with ESMTP id 27ygup1kx3-1
for ; Tue, 17 Jan 2017 19:11:51 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd3-us-west.apache.org
 (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 012E81827B3   
for
 ; Wed, 18 Jan 2017 00:11:51 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])   by localhost
 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with 
ESMTP
 id Kv0DFgduNRaC for ; Wed, 18 Jan 2017 00:11:49
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-us.apache.org (ASF Mail Server at
 mx1-lw-us.apache.org) with ESMTP id 1EADF5FAF3 for ;
 Wed, 18 Jan 2017 00:11:49 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id C1331E867Dfor
 ; Wed, 18 Jan 2017 00:11:28 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id 5C69325290  for ; Wed, 18 Jan 2017 00:11:27 +
 (UTC)
Date: Wed, 18 Jan 2017 00:11:27 +
From: "Steve Rowe (JIRA)" 
To: 
Message-ID: 
In-Reply-To: 
References:  

Subject: [jira] [Issue Comment Deleted] (SOLR-8029) Modernize and
 standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGx0ZEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGx8ZcRkZEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThdgG0wHRUlrHGwTZxJIYUxuQF9Ma1 
JIHx1wbU54bEFleBEKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsaGgQeEgQfEBseGh8aEQpeWRd6X
 mxOQxEKTVwXGRwSEQpMWhdoaU1NXREKTEYXbGtrEQpDWhcYGhMEGxISBBseBBseGBEKQl4XGxEK 
QkYXZkRZe0hyeUByTEwRCkJFF28FYGZZXWhASx9GEQpCThdhQEITQ1NrRWZSRhEKQkwXbAVGfh0 
cGH1Ob0gRCkJsF2luSEx7SWlaTn5OEQpCQBduHxpFYXJMQVpYaREKQlgXemRyS2d7Hnp9ZXMRCl
 pYFxkRCnBnF21GUkBafWJvfgVjEBoRCnBoF3pAXB1pE1lLbBxnEBoRCnBoF2dhWBJMEmwScEx+E 
BoRCnBoF2dPGmgabBsTbGV/EBoRCnBoF2EeQXkaeEceXE5wEBoRCnBoF2FAYmcbXR4cbBJ+EBoR 
CnB/F2keXntgZXlDYkgFEBsbExEKcF8XYHtpGktIUGEYTnkQHBoRCnB9F2NZTF99H2ITZHhbEBo
 RCnBnF3p7Uhpka0h8TkxhEBkaEQpwZxdgc05kARhZHFxlHhAZGhEKcGcXZVh+EhNHXmdQRn0QGR 
oRCnB9F2Zub058bn1BQEZNEB4SEQpwfxd6e38cbl9Sc34TRRAfGxEKcF8XYW8bWUkZRXl5bx8QH 
hIRCnB9F2RkbF9bcnhzS2xBEB4SEQpwbBdnYUdta0hCEmJ5aBAaEQpwQxdjXnMTZwFGbHpQbBAd 
GhEKbX4XGhEKWE0XSxEg
Content-Transfer-Encoding: Quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, 
definitions=2017-01-17_16:,,
 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=0 
malwarescore=0
 

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827110#comment-15827110
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

postmas...@opentext.net
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.







Diagnostic information for administrators:

Generating server: opentext.net

postmas...@opentext.net
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Original message headers:

Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by
 otwlxg12.opentext.net (10.2.103.213) with Microsoft SMTP Server (TLS) id
 14.3.319.2; Tue, 17 Jan 2017 19:11:38 -0500
Received: from mx0a-00102601.pphosted.com (mx0b-00102601.pphosted.com
 [67.231.152.222])  by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I0Bcbc007496  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for ; Tue, 17 Jan 2017 19:11:39 -0500
Received: from pps.filterd (m0001253.ppops.net [127.0.0.1]) by
 mx0b-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I0BTKV025583
for ; Tue, 17 Jan 2017 19:11:38 -0500
Received: from spamd1-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0b-00102601.pphosted.com with ESMTP id 27ydm4wmku-1
for ; Tue, 17 Jan 2017 19:11:38 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd1-us-west.apache.org
 (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id DD5D7C0ECF
for
 ; Wed, 18 Jan 2017 00:11:37 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])   by localhost
 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)  with 
ESMTP
 id s8miHzESFHJY for ; Wed, 18 Jan 2017 00:11:36
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-us.apache.org (ASF Mail Server at
 mx1-lw-us.apache.org) with ESMTP id 124555FDEA for ;
 Wed, 18 Jan 2017 00:11:34 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id AAE12EAAE0for
 ; Wed, 18 Jan 2017 00:11:30 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id 5E807252AC  for ; Wed, 18 Jan 2017 00:11:29 +
 (UTC)
Date: Wed, 18 Jan 2017 00:11:29 +
From: "Steve Rowe (JIRA)" 
To: 
Message-ID: 
In-Reply-To: 
References:  

Subject: [jira] [Issue Comment Deleted] (SOLR-8029) Modernize and
 standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGBgaEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGBoacRMSEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThdeS0geRl97YWYSTmlCaG1db10ZSU 
ATTX8TcEFeQ0RGbhEKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsbGgQeEgQSHBAbHhofGhEKXlkXe
 l5sTnwRCk1cFxgaGREKTFoXaGlNTV0RCkxGF2xraxEKQ1oXGBoTBBsSEgQbHgQbHhgRCkJeFxsR 
CkJGF2ZEWXtIcnlAckxMEQpCRRdvBWBmWV1oQEsfRhEKQk4XYUBCE0NTa0VmUkYRCkJMF2wFRn4 
dHBh9Tm9IEQpCbBdpbkhMe0lpWk5+ThEKQkAXbh8aRWFyTEFaWGkRCkJYF3pkcktnex56fWVzEQ
 pNXhcbEQpaWBcZEQpwZxdtRlJAWn1ib34FYxAaEQpwaBdmWmB8U2JLY00YRxAaEQpwaBdjf1xcS 
EVLbhp9ehAaEQpwaBdtXxpFR1J6RmVSXxAaEQpwaBdhcnpzAR1zW0tEbRAaEQpwaBdmcGFLHEJb 
BUF6ZxAaEQpwfxdpHl57YGV5Q2JIBRAbGRwRCnBfF2B7aRpLSFBhGE55EBwaEQpwfRdjWUxffR9
 iE2R4WxAaEQpwZxd6e1IaZGtIfE5MYRAaEQpwZxdgc05kARhZHFxlHhAaEQpwZxdlWH4SE0deZ1 
BGfRAaEQpwfRdmbm9OfG59QUBGTRAeEhEKcH8Xent/HG5fUnN+E0UQHhwRCnBfF2FvG1lJGUV5e 
W8fEB4SEQpwfRdkZGxfW3J4c0tsQRAeEhEKcGwXZ2FHbWtIQhJieWgQGhEKcEMXY15zE2cBRmx6
 UGwQHRoRCm1+FxsRClhNF0sRIA==
Content-Transfer-Encoding: Quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, 
definitions=2017-01-17_17:,,
 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=0 

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827112#comment-15827112
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

postmas...@opentext.net
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.







Diagnostic information for administrators:

Generating server: opentext.net

postmas...@opentext.net
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Original message headers:

Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by
 otwlxg10.opentext.net (10.2.103.151) with Microsoft SMTP Server id
 14.3.319.2; Tue, 17 Jan 2017 19:11:37 -0500
Received: from mx0a-00102601.pphosted.com (mx0b-00102601.pphosted.com
 [67.231.152.222])  by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I0Bbed007477  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for ; Tue, 17 Jan 2017 19:11:37 -0500
Received: from pps.filterd (m0044805.ppops.net [127.0.0.1]) by
 mx0b-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I0BRcD024693
for ; Tue, 17 Jan 2017 19:11:37 -0500
Received: from spamd1-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0b-00102601.pphosted.com with ESMTP id 27ygp0w04b-1
for ; Tue, 17 Jan 2017 19:11:37 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd1-us-west.apache.org
 (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 81437C174C
for
 ; Wed, 18 Jan 2017 00:11:36 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])   by localhost
 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)  with 
ESMTP
 id abTI3UGlWbgg for ; Wed, 18 Jan 2017 00:11:34
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-us.apache.org (ASF Mail Server at
 mx1-lw-us.apache.org) with ESMTP id 4DA5D60E3B for ;
 Wed, 18 Jan 2017 00:11:33 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id 4897CEAACDfor
 ; Wed, 18 Jan 2017 00:11:30 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id CB9C6252A7  for ; Wed, 18 Jan 2017 00:11:28 +
 (UTC)
Date: Wed, 18 Jan 2017 00:11:28 +
From: "Steve Rowe (JIRA)" 
To: 
Message-ID: 
In-Reply-To: 
References:  

Subject: [jira] [Issue Comment Deleted] (SOLR-8029) Modernize and
 standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGBsTEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGxMTcRMdEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThdtbGBIWEttfUsTRnpke3xkbW4dW0 
5oc2B9G1JnQGtJcxEKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsbGgQeEgQSHBAbHhofGhEKXlkXe
 l5sTn8RCk1cFxgfHREKTFoXaWhpTU1dEQpMRhdsa2sRCkNaFxgaEwQbEhIEGx4EGx4YEQpCXhcb 
EQpCRhdmRFl7SHJ5QHJMTBEKQkUXbwVgZlldaEBLH0YRCkJOF2FAQhNDU2tFZlJGEQpCTBdsBUZ 
+HRwYfU5vSBEKQmwXaW5ITHtJaVpOfk4RCkJAF24fGkVhckxBWlhpEQpCWBd6ZHJLZ3seen1lcx
 EKTV4XGxEKWlgXGREKcGcXbUZSQFp9Ym9+BWMQGhEKcGgXYR5BeRp4Rx5cTnAQGhEKcGgXYUxfb 
EJeYwVcBXsQGhEKcGgXbUAYTFNFYGJeTRoQGhEKcGgXZUlLX25sYRldQnkQGhEKcGgXbx1PeBli 
W3xtWk8QGhEKcH8XaR5ee2BleUNiSAUQGxkcEQpwXxdge2kaS0hQYRhOeRAcGhEKcH0XY1lMX30
 fYhNkeFsQGhEKcGcXentSGmRrSHxOTGEQGhEKcGcXYHNOZAEYWRxcZR4QGhEKcGcXZVh+EhNHXm 
dQRn0QGhEKcH0XZm5vTnxufUFARk0QHhIRCnB/F3p7fxxuX1JzfhNFEB4cEQpwXxdhbxtZSRlFe 
XlvHxAeEhEKcH0XZGRsX1tyeHNLbEEQHhIRCnBsF2dhR21rSEISYnloEBoRCnBDF2NecxNnAUZs
 elBsEB0aEQptfhcbEQpYTRdLESA=
Content-Transfer-Encoding: Quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, 
definitions=2017-01-17_17:,,
 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=0 
malwarescore=0
 

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827111#comment-15827111
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

postmas...@opentext.net
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.







Diagnostic information for administrators:

Generating server: opentext.net

postmas...@opentext.net
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Original message headers:

Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by
 otwlxg11.opentext.net (10.2.103.152) with Microsoft SMTP Server id
 14.3.319.2; Tue, 17 Jan 2017 19:11:43 -0500
Received: from mx0a-00102601.pphosted.com (mx0a-00102601.pphosted.com
 [67.231.144.228])  by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I0Bg0I007527  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for ; Tue, 17 Jan 2017 19:11:43 -0500
Received: from pps.filterd (m825.ppops.net [127.0.0.1]) by
 mx0a-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I033NJ017310
for ; Tue, 17 Jan 2017 19:11:42 -0500
Received: from spamd4-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0a-00102601.pphosted.com with ESMTP id 27ye4gahxy-1
for ; Tue, 17 Jan 2017 19:11:42 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd4-us-west.apache.org
 (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E73A1C0744
for
 ; Wed, 18 Jan 2017 00:11:41 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-eu.apache.org ([10.40.0.8])   by localhost
 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with 
ESMTP
 id Epmuz9ndxBZS for ; Wed, 18 Jan 2017 00:11:39
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-eu.apache.org (ASF Mail Server at
 mx1-lw-eu.apache.org) with ESMTP id E37095F47A for ;
 Wed, 18 Jan 2017 00:11:36 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id 5532BE8F2Afor
 ; Wed, 18 Jan 2017 00:11:29 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id E8AE52528A  for ; Wed, 18 Jan 2017 00:11:27 +
 (UTC)
Date: Wed, 18 Jan 2017 00:11:27 +
From: "Steve Rowe (JIRA)" 
To: 
Message-ID: 
In-Reply-To: 
References:  

Subject: [jira] [Issue Comment Deleted] (SOLR-8029) Modernize and
 standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGx0ZEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGx8ZcRkZEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThdZHX4cY3BnXnJ/YxlEQh59W0NrQx 
Jde0tPXhtOWkZ7WREKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsaGgQeEgQfEBseGh8aEQpeWRd6X
 mxOcBEKTVwXGB0bEQpMWhdoaU1NXREKTEYXbGtrEQpDWhcYGhMEGxISBBseBBseGBEKQl4XGxEK 
QkYXZkRZe0hyeUByTEwRCkJFF28FYGZZXWhASx9GEQpCThdhQEITQ1NrRWZSRhEKQkwXbAVGfh0 
cGH1Ob0gRCkJsF2luSEx7SWlaTn5OEQpCQBduHxpFYXJMQVpYaREKQlgXemRyS2d7Hnp9ZXMRCk
 1eFxsRClpYFxkRCnBnF21GUkBafWJvfgVjEBoRCnBoF2tDGV17fxITZGhNEBoRCnBoF2EeQXkae 
EceXE5wEBoRCnBoF29uUAUYcBtvaRN5EBoRCnBoF2x5HGZvW2RDGmleEBoRCnBoF29uUHpiGBtc 
Qn9OEBoRCnB/F2keXntgZXlDYkgFEBsbExEKcF8XYHtpGktIUGEYTnkQHBoRCnB9F2NZTF99H2I
 TZHhbEBoRCnBnF3p7Uhpka0h8TkxhEBkaEQpwZxdgc05kARhZHFxlHhAZGhEKcGcXZVh+EhNHXm 
dQRn0QGRoRCnB9F2Zub058bn1BQEZNEB4SEQpwfxd6e38cbl9Sc34TRRAfGxEKcF8XYW8bWUkZR 
Xl5bx8QHhIRCnB9F2RkbF9bcnhzS2xBEB4SEQpwbBdnYUdta0hCEmJ5aBAaEQpwQxdjXnMTZwFG
 bHpQbBAdGhEKbX4XGxEKWE0XSxEg
Content-Transfer-Encoding: Quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, 
definitions=2017-01-17_16:,,
 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=0 
malwarescore=0
 

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827113#comment-15827113
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

steve.mol...@opentext.com<mailto:steve.mol...@opentext.com>
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.

The following organization rejected your message: wlsvc01.opentext.com.







Diagnostic information for administrators:

Generating server: opentext.net

steve.mol...@opentext.com
wlsvc01.opentext.com #550 5.1.1 <steve.mol...@opentext.com>... User unknown ##

Original message headers:

Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by
 otwlxg11.opentext.net (10.2.103.152) with Microsoft SMTP Server id
 14.3.319.2; Tue, 17 Jan 2017 19:10:36 -0500
Received: from mx0a-00102601.pphosted.com (mx0a-00102601.pphosted.com
 [67.231.144.228])  by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I0AZ6Y007068  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:10:36 -0500
Received: from pps.filterd (m803.ppops.net [127.0.0.1]) by
 mx0a-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I08KXa027875
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:10:35 -0500
Received: from spamd2-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0a-00102601.pphosted.com with ESMTP id 27ygup1kms-1
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:10:34 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd2-us-west.apache.org
 (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 97F7A1A0317   
for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:10:33 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])   by localhost
 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)  with 
ESMTP
 id eJMGVLW-9cyn for <steve.mol...@opentext.com>;   Wed, 18 Jan 2017 
00:10:32
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-us.apache.org (ASF Mail Server at
 mx1-lw-us.apache.org) with ESMTP id A5BC55FDEA for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:10:30 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id 6C6CBE8687for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:10:28 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id C401425292  for <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:10:26
 + (UTC)
Date: Wed, 18 Jan 2017 00:10:26 +
From: "postmas...@opentext.net (JIRA)" <j...@apache.org>
To: <steve.mol...@opentext.com>
Message-ID: <jira.12863036.144132000.34367.1484698226...@atlassian.jira>
In-Reply-To: <jira.12863036.144132...@atlassian.jira>
References: <jira.12863036.144132...@atlassian.jira> 
<jira.12863036.1441888832...@jira-lw-us.apache.org>
Subject: [jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGx0YEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGx8YcRkYEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThdmHVh5RUcdHBNuT3hcGBJ7SV5BWW 
sSRFBBHnNZUGFiHxEKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsaGgQeEgQfEBseGh8aEQpeWRd6X
 mxJfBEKTVwXGRkcEQpMWhdpTU1TEQpMRhdsa2sRCkNaFxgaEwQbEhIEGx4EGx4YEQpCXhcbEQpC 
RhdmRFl7SHJ5QHJMTBEKQkUXYXxOHn1ABXtYAX4RCkJOF2FAQhNDU2tFZlJGEQpCTBdsBUZ+HRw 
YfU5vSBEKQmwXZxtlSGQablJNYAURCkJAF2QBARpTeUBZfB9TEQpCWBdoTnNBTH5yWEkYfxEKWl
 gXGREKcGcXaHhOZnBMTk9ZE0UQGRoRCnBoF2dhWBJMEmwScEx+EBoRCnBoF2UTBUZkb3tpbFhPE 
BoRCnBoF2dPGmgabBsTbGV/EBoRCnBoF2EeQXkaeEceXE5wEBoRCnBoF2NYc35rTnMeH39tEBoR 
CnB/F2keXntgZXlDYkgFEBsbExEKcF8XYHtpGktIUGEYTnkQHBoRCnB9F2hMclgdZ1pwG2FmEBo
 RCnBnF3p7Uhpka0h8TkxhEBkaEQpwZxdgc05kARhZHFxlHhAZGhEKcGcXZVh+EhNHXmdQRn0QGR 
oRCnB9F2Zub058bn1BQEZNEB4SEQpwfxd6e38cbl9Sc34TRRAfGxEKcF8XYW8bWUkZRXl5bx8QH 
hIRCnB9F2RkbF9bcnhzS2xBEB4SEQpwbBdgQH5iZU1caH9LbxAZGhEKcEMXY15zE2cBRmx6UGwQ 
HRoRCm1+FxoRClhNF0sRIA==
Content-Transfer-Encod

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827109#comment-15827109
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

postmas...@opentext.net
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.







Diagnostic information for administrators:

Generating server: opentext.net

postmas...@opentext.net
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Original message headers:

Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by
 otwlxg11.opentext.net (10.2.103.152) with Microsoft SMTP Server id
 14.3.319.2; Tue, 17 Jan 2017 19:11:37 -0500
Received: from mx0a-00102601.pphosted.com (mx0a-00102601.pphosted.com
 [67.231.144.228])  by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I0BaoN007465  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for ; Tue, 17 Jan 2017 19:11:37 -0500
Received: from pps.filterd (m803.ppops.net [127.0.0.1]) by
 mx0a-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I02GXt023608
for ; Tue, 17 Jan 2017 19:11:36 -0500
Received: from spamd1-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0a-00102601.pphosted.com with ESMTP id 27ygup1kvk-1
for ; Tue, 17 Jan 2017 19:11:35 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd1-us-west.apache.org
 (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id CBEC2C1757
for
 ; Wed, 18 Jan 2017 00:11:34 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])   by localhost
 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)  with 
ESMTP
 id BHHp874CHKH7 for ; Wed, 18 Jan 2017 00:11:33
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-us.apache.org (ASF Mail Server at
 mx1-lw-us.apache.org) with ESMTP id 342BD5FAF3 for ;
 Wed, 18 Jan 2017 00:11:32 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id CB2F1EAAB3for
 ; Wed, 18 Jan 2017 00:11:29 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id 5E37425284  for ; Wed, 18 Jan 2017 00:11:28 +
 (UTC)
Date: Wed, 18 Jan 2017 00:11:28 +
From: "Steve Rowe (JIRA)" 
To: 
Message-ID: 
In-Reply-To: 
References:  

Subject: [jira] [Issue Comment Deleted] (SOLR-8029) Modernize and
 standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGx0ZEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGx8ZcRkZEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThdvHHh+B2Becl1EB2x/XGZ4bUl8f0 
dzQl5cWm1iaXsabREKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsaGgQeEgQfEBseGh8aEQpeWRd6X
 mxOeREKTVwXGR4fEQpMWhdoaU1NXREKTEYXbGtrEQpDWhcYGhMEGxISBBseBBseGBEKQl4XGxEK 
QkYXZkRZe0hyeUByTEwRCkJFF28FYGZZXWhASx9GEQpCThdhQEITQ1NrRWZSRhEKQkwXbAVGfh0 
cGH1Ob0gRCkJsF2luSEx7SWlaTn5OEQpCQBduHxpFYXJMQVpYaREKQlgXemRyS2d7Hnp9ZXMRCl
 pYFxkRCnBnF21GUkBafWJvfgVjEBoRCnBoF2Z4a39TZG9hZX19EBoRCnBoF2EeQXkaeEceXE5wE 
BoRCnBoF2t4GBhnT3gaGWxEEBoRCnBoF2tFZmJhTmRvfx9kEBoRCnBoF2VBc35FbmtjXVBfEBoR 
CnB/F2keXntgZXlDYkgFEBsbExEKcF8XYHtpGktIUGEYTnkQHBoRCnB9F2NZTF99H2ITZHhbEBo
 RCnBnF3p7Uhpka0h8TkxhEBkaEQpwZxdgc05kARhZHFxlHhAZGhEKcGcXZVh+EhNHXmdQRn0QGR 
oRCnB9F2Zub058bn1BQEZNEB4SEQpwfxd6e38cbl9Sc34TRRAfGxEKcF8XYW8bWUkZRXl5bx8QH 
hIRCnB9F2RkbF9bcnhzS2xBEB4SEQpwbBdnYUdta0hCEmJ5aBAaEQpwQxdjXnMTZwFGbHpQbBAd 
GhEKbX4XGhEKWE0XSxEg
Content-Transfer-Encoding: Quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, 
definitions=2017-01-17_16:,,
 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=0 
malwarescore=0
 

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827104#comment-15827104
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

steve.mol...@opentext.com<mailto:steve.mol...@opentext.com>
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.

The following organization rejected your message: wlsvc01.opentext.com.







Diagnostic information for administrators:

Generating server: opentext.net

steve.mol...@opentext.com
wlsvc01.opentext.com #550 5.1.1 <steve.mol...@opentext.com>... User unknown ##

Original message headers:

Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by
 otwlxg12.opentext.net (10.2.103.213) with Microsoft SMTP Server (TLS) id
 14.3.319.2; Tue, 17 Jan 2017 19:09:32 -0500
Received: from mx0a-00102601.pphosted.com (mx0a-00102601.pphosted.com
 [67.231.144.228])  by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I09WNb006625  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:09:32 -0500
Received: from pps.filterd (m803.ppops.net [127.0.0.1]) by
 mx0a-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I08KX9027875
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:09:31 -0500
Received: from spamd4-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0a-00102601.pphosted.com with ESMTP id 27ygup1kd2-1
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:09:31 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd4-us-west.apache.org
 (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 74559C0744
for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:09:31 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])   by localhost
 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with 
ESMTP
 id Pyvx_zxE29FB for <steve.mol...@opentext.com>;   Wed, 18 Jan 2017 
00:09:29
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-us.apache.org (ASF Mail Server at
 mx1-lw-us.apache.org) with ESMTP id 4FD825FCA2 for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:09:29 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id 405E1E8679for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:09:28 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id A30CE2528F  for <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:09:26
 + (UTC)
Date: Wed, 18 Jan 2017 00:09:26 +
From: "postmas...@opentext.net (JIRA)" <j...@apache.org>
To: <steve.mol...@opentext.com>
Message-ID: <jira.12863036.144132000.34336.1484698166...@atlassian.jira>
In-Reply-To: <jira.12863036.144132...@atlassian.jira>
References: <jira.12863036.144132...@atlassian.jira> 
<jira.12863036.1441888832...@jira-lw-us.apache.org>
Subject: [jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGx0YEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGx8YcRkYEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThdwGR9wR2NQUEdGHWJuc2JDbElebU 
ZoElJbGF95Ehl9XxEKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsaGgQeEgQfEBseGh8aEQpeWRd6X
 mxIfREKTVwXGBMcEQpMWhdpTU1TEQpMRhdsa2sRCkNaFxgaEwQbEhIEGx4EGx4YEQpCXhcbEQpC 
RhdmRFl7SHJ5QHJMTBEKQkUXYXxOHn1ABXtYAX4RCkJOF2FAQhNDU2tFZlJGEQpCTBdsBUZ+HRw 
YfU5vSBEKQmwXZxtlSGQablJNYAURCkJAF2QBARpTeUBZfB9TEQpCWBdoTnNBTH5yWEkYfxEKTV
 4XGxEKWlgXGREKcGcXaHhOZnBMTk9ZE0UQGRoRCnBoF2tDGV17fxITZGhNEBoRCnBoF2EeQXkae 
EceXE5wEBoRCnBoF29uUAUYcBtvaRN5EBoRCnBoF2x5HGZvW2RDGmleEBoRCnBoF2wYUGJNXwFm 
Y19AEBoRCnB/F2keXntgZXlDYkgFEBsbExEKcF8XYHtpGktIUGEYTnkQHBoRCnB9F2lPSUJren1
 /QxliEBoRCnBnF3p7Uhpka0h8TkxhEBkaEQpwZxdgc05kARhZHFxlHhAZGhEKcGcXZVh+EhNHXm 
dQRn0QGRoRCnB9F2Zub058bn1BQEZNEB4SEQpwfxd6e38cbl9Sc34TRRAfGxEKcF8XYW8bWUkZR 
Xl5bx8QHhIRCnB9F2RkbF9bcnhzS2xBEB4SEQpwbBdgQH5iZU1caH9LbxAZGhEKcEMXY15zE2cB
 Rmx6UGwQHRoRCm1+FxsRClhNF0sRIA==
Conten

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827102#comment-15827102
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

steve.mol...@opentext.com<mailto:steve.mol...@opentext.com>
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.

The following organization rejected your message: wlsvc01.opentext.com.







Diagnostic information for administrators:

Generating server: opentext.net

steve.mol...@opentext.com
wlsvc01.opentext.com #550 5.1.1 <steve.mol...@opentext.com>... User unknown ##

Original message headers:

Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by
 otwlxg11.opentext.net (10.2.103.152) with Microsoft SMTP Server id
 14.3.319.2; Tue, 17 Jan 2017 19:08:35 -0500
Received: from mx0a-00102601.pphosted.com (mx0a-00102601.pphosted.com
 [67.231.144.228])  by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I08YoL006337  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:08:34 -0500
Received: from pps.filterd (m825.ppops.net [127.0.0.1]) by
 mx0a-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I032dd017297
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:08:34 -0500
Received: from spamd1-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0a-00102601.pphosted.com with ESMTP id 27ye4gah50-1
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:08:33 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd1-us-west.apache.org
 (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 6DE10C259D
for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:08:33 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])   by localhost
 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)  with 
ESMTP
 id KaHZ2sxc65Ju for <steve.mol...@opentext.com>;   Wed, 18 Jan 2017 
00:08:31
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-us.apache.org (ASF Mail Server at
 mx1-lw-us.apache.org) with ESMTP id 668315FE35 for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:08:30 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id 913BCE8688for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:08:28 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id A5FDB2528F  for <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:08:26
 + (UTC)
Date: Wed, 18 Jan 2017 00:08:26 +
From: "postmas...@opentext.net (JIRA)" <j...@apache.org>
To: <steve.mol...@opentext.com>
Message-ID: <jira.12863036.144132000.34305.1484698106...@atlassian.jira>
In-Reply-To: <jira.12863036.144132...@atlassian.jira>
References: <jira.12863036.144132...@atlassian.jira> 
<jira.12863036.1441888832...@jira-lw-us.apache.org>
Subject: [jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGx0YEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGx8YcRkYEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThdNfXxYWUF8XGFidUNfRXlMfE9QXU 
4eXlhYXxN8e3trRhEKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsaGgQeEgQfEBseGh8aEQpeWRd6X
 mxLSREKTVwXGRseEQpMWhdpTU1TEQpMRhdsa2sRCkNaFxgaEwQbEhIEGx4EGx4YEQpCXhcbEQpC 
RhdmRFl7SHJ5QHJMTBEKQkUXYXxOHn1ABXtYAX4RCkJOF2FAQhNDU2tFZlJGEQpCTBdsBUZ+HRw 
YfU5vSBEKQmwXZxtlSGQablJNYAURCkJAF2QBARpTeUBZfB9TEQpCWBdoTnNBTH5yWEkYfxEKWl
 gXGREKcGcXaHhOZnBMTk9ZE0UQGRoRCnBoF2Z4a39TZG9hZX19EBoRCnBoF2EeQXkaeEceXE5wE 
BoRCnBoF2t4GBhnT3gaGWxEEBoRCnBoF2tFZmJhTmRvfx9kEBoRCnBoF2loGl5BemB6X19lEBoR 
CnB/F2keXntgZXlDYkgFEBsbExEKcF8XYHtpGktIUGEYTnkQHBoRCnB9F3oFfFBeGRthRX4FEBo
 RCnBnF3p7Uhpka0h8TkxhEBkaEQpwZxdgc05kARhZHFxlHhAZGhEKcGcXZVh+EhNHXmdQRn0QGR 
oRCnB9F2Zub058bn1BQEZNEB4SEQpwfxd6e38cbl9Sc34TRRAfGBEKcF8XYW8bWUkZRXl5bx8QH 
hIRCnB9F2RkbF9bcnhzS2xBEB4SEQpwbBdgQH5iZU1caH9LbxAZGhEKcEMXY15zE2cBRmx6UGwQ 
HRoRCm1+FxoRClhNF0sRIA==
Content-Transfer-Encod

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827099#comment-15827099
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

steve.mol...@opentext.com<mailto:steve.mol...@opentext.com>
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.

The following organization rejected your message: wlsvc01.opentext.com.







Diagnostic information for administrators:

Generating server: opentext.net

steve.mol...@opentext.com
wlsvc01.opentext.com #550 5.1.1 <steve.mol...@opentext.com>... User unknown ##

Original message headers:

Received: from wldmzsvc05.dmz.opentext.com (10.2.170.16) by
 otwlxg10.opentext.net (10.2.103.151) with Microsoft SMTP Server id
 14.3.319.2; Tue, 17 Jan 2017 19:05:33 -0500
Received: from mx0a-00102601.pphosted.com (mx0b-00102601.pphosted.com
 [67.231.152.222])  by wldmzsvc05.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I05XYI017337  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:05:33 -0500
Received: from pps.filterd (m0044805.ppops.net [127.0.0.1]) by
 mx0b-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I01Iq4018414
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:05:32 -0500
Received: from spamd4-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0b-00102601.pphosted.com with ESMTP id 27ygp0vyrd-1
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:05:32 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd4-us-west.apache.org
 (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 28D35C0333
for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:05:32 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])   by localhost
 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with 
ESMTP
 id JEjR3tmFDoh6 for <steve.mol...@opentext.com>;   Wed, 18 Jan 2017 
00:05:30
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-us.apache.org (ASF Mail Server at
 mx1-lw-us.apache.org) with ESMTP id 444575FE0C for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:05:29 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id 54351E866Ffor
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:05:28 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id 8FA0A2528F  for <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:05:26
 + (UTC)
Date: Wed, 18 Jan 2017 00:05:26 +
From: "postmas...@opentext.net (JIRA)" <j...@apache.org>
To: <steve.mol...@opentext.com>
Message-ID: <jira.12863036.144132000.34260.1484697926...@atlassian.jira>
In-Reply-To: <jira.12863036.144132...@atlassian.jira>
References: <jira.12863036.144132...@atlassian.jira> 
<jira.12863036.1441888832...@jira-lw-us.apache.org>
Subject: [jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGBsTEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGxMTcRMcEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThceHWNtfXJsB2hEW1NbG39efGBtfE 
NoB0B+QH9/RmteUhEKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsbGgQeEgQSHBAbHhofGhEKXlkXe
 l5sckQRCk1cFxgSHREKTFoXaU1NUxEKTEYXbGtrEQpDWhcYGhMEGxISBBseBBseGBEKQl4XGxEK 
QkYXZkRZe0hyeUByTEwRCkJFF2F8Th59QAV7WAF+EQpCThdhQEITQ1NrRWZSRhEKQkwXbAVGfh0 
cGH1Ob0gRCkJsF2cbZUhkGm5STWAFEQpCQBdkAQEaU3lAWXwfUxEKQlgXaE5zQUx+clhJGH8RCk
 1eFxsRClpYFxkRCnBnF2h4TmZwTE5PWRNFEBoRCnBoF2EeQXkaeEceXE5wEBoRCnBoF2FMX2xCX 
mMFXAV7EBoRCnBoF21AGExTRWBiXk0aEBoRCnBoF2VJS19ubGEZXUJ5EBoRCnBoF216GFN6H25k 
bk5fEBoRCnB/F2keXntgZXlDYkgFEBsZHBEKcF8XYHtpGktIUGEYTnkQHBoRCnB9F25TSVBgfUh
 /WRxQEBoRCnBnF3p7Uhpka0h8TkxhEBoRCnBnF2BzTmQBGFkcXGUeEBoRCnBnF2VYfhITR15nUE 
Z9EBoRCnB9F2Zub058bn1BQEZNEB4SEQpwfxd6e38cbl9Sc34TRRAeEhEKcF8XYW8bWUkZRXl5b 
x8QHhIRCnB9F2RkbF9bcnhzS2xBEB4SEQpwbBdgQH5iZU1caH9LbxAaEQpwQxdjXnMTZwFGbHpQ 
bBAdGhEKbX4XGxEKWE0XSxEg
Content-Transfer-Encod

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827096#comment-15827096
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

steve.mol...@opentext.com<mailto:steve.mol...@opentext.com>
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.

The following organization rejected your message: wlsvc01.opentext.com.







Diagnostic information for administrators:

Generating server: opentext.net

steve.mol...@opentext.com
wlsvc01.opentext.com #550 5.1.1 <steve.mol...@opentext.com>... User unknown ##

Original message headers:

Received: from wldmzsvc05.dmz.opentext.com (10.2.170.16) by
 otwlxg10.opentext.net (10.2.103.151) with Microsoft SMTP Server id
 14.3.319.2; Tue, 17 Jan 2017 19:03:36 -0500
Received: from mx0a-00102601.pphosted.com (mx0a-00102601.pphosted.com
 [67.231.144.228])  by wldmzsvc05.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I03Z5g016278  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:03:35 -0500
Received: from pps.filterd (m803.ppops.net [127.0.0.1]) by
 mx0a-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I02GUa023608
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:03:34 -0500
Received: from spamd4-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0a-00102601.pphosted.com with ESMTP id 27ygup1j3u-1
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:03:34 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd4-us-west.apache.org
 (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 55B85C0333
for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:03:33 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999,
URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5]
autolearn=disabled
Received: from mx1-lw-eu.apache.org ([10.40.0.8])   by localhost
 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with 
ESMTP
 id P3XspN1L5W48 for <steve.mol...@opentext.com>;   Wed, 18 Jan 2017 
00:03:31
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-eu.apache.org (ASF Mail Server at
 mx1-lw-eu.apache.org) with ESMTP id AF5A65FB5D for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:03:30 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id D76AEE867Efor
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:03:28 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id C8DEA25294  for <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:03:26
 + (UTC)
Date: Wed, 18 Jan 2017 00:03:26 +
From: "postmas...@opentext.net (JIRA)" <j...@apache.org>
To: <steve.mol...@opentext.com>
Message-ID: <jira.12863036.144132000.34230.1484697806...@atlassian.jira>
In-Reply-To: <jira.12863036.144132...@atlassian.jira>
References: <jira.12863036.144132...@atlassian.jira> 
<jira.12863036.1441888832...@jira-lw-us.apache.org>
Subject: [jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGxwSEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGx4ScR8SEBp3Bhg 
aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThdPWWkdT29BG2RcQ2IefVBYG1liWn 
N9b0RneX11ex1beBEKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsaGgQeEgQfEBseGh8aEQpeWRd6X
 mx8UhEKTVwXGBgTEQpMWhdpTU1TEQpMRhdsa2sRCkNaFxgaEwQbEhIEGx4EGx4YEQpCXhcbEQpC 
RhdmRFl7SHJ5QHJMTBEKQkUXYXxOHn1ABXtYAX4RCkJOF2FAQhNDU2tFZlJGEQpCTBdsBUZ+HRw 
YfU5vSBEKQmwXZxtlSGQablJNYAURCkJAF2QBARpTeUBZfB9TEQpCWBdoTnNBTH5yWEkYfxEKTV
 4XGxEKWlgXGREKcGcXaHhOZnBMTk9ZE0UQGRoRCnBoF2ZaYHxTYktjTRhHEBkaEQpwaBdjf1xcS 
EVLbhp9ehAZGhEKcGgXbV8aRUdSekZlUl8QGRoRCnBoF2FyenMBHXNbS0RtEBkaEQpwaBdmcGFL 
HEJbBUF6ZxAZGhEKcH8XaR5ee2BleUNiSAUQGxsSEQpwXxdge2kaS0hQYRhOeRAcGhEKcH0XZUZ
 9eVAaXm9acF0QGRoRCnBnF3p7Uhpka0h8TkxhEBkaEQpwZxdgc05kARhZHFxlHhAZGhEKcGcXZV 
h+EhNHXmdQRn0QGRoRCnB9F2Zub058bn1BQEZNEB4SEQpwfxd6e38cbl9Sc34TRRAfHhEKcF8XY 
W8bWUkZRXl5bx8QHhIRCnB9F2RkbF9bcnhzS2xBEB4SEQpwbBdgQH5iZU1caH9LbxAZGhEKcEMX
 Y15zE2cBRmx6UGwQHRoRCm1+FxsRClhNF0sRIA==
Conten

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[postmas...@opentext.net (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827094#comment-15827094
 ] 

postmas...@opentext.net commented on SOLR-8029:
---

Delivery has failed to these recipients or groups:

steve.mol...@opentext.com<mailto:steve.mol...@opentext.com>
The e-mail address you entered couldn't be found. Please check the recipient's 
e-mail address and try to resend the message. If the problem continues, please 
contact your helpdesk.

The following organization rejected your message: wlsvc01.opentext.com.







Diagnostic information for administrators:

Generating server: opentext.net

steve.mol...@opentext.com
wlsvc01.opentext.com #550 5.1.1 <steve.mol...@opentext.com>... User unknown ##

Original message headers:

Received: from wldmzsvc05.dmz.opentext.com (10.2.170.16) by
 otwlxg11.opentext.net (10.2.103.152) with Microsoft SMTP Server id
 14.3.319.2; Tue, 17 Jan 2017 19:00:37 -0500
Received: from mx0a-00102601.pphosted.com (mx0b-00102601.pphosted.com
 [67.231.152.222])  by wldmzsvc05.dmz.opentext.com (8.14.4/8.14.4) with 
ESMTP
 id v0I00bmr014287  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 
verify=NO)
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:00:37 -0500
Received: from pps.filterd (m0001253.ppops.net [127.0.0.1]) by
 mx0b-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0HNpCIj011782
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:00:37 -0500
Received: from spamd1-us-west.apache.org (pnap-us-west-generic-nat.apache.org
 [209.188.14.142])  by mx0b-00102601.pphosted.com with ESMTP id 27ydm4wkba-1
for <steve.mol...@opentext.com>; Tue, 17 Jan 2017 19:00:36 -0500
Received: from localhost (localhost [127.0.0.1])by 
spamd1-us-west.apache.org
 (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id DC15EC2593
for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:00:35 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31
tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999]
autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])   by localhost
 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)  with 
ESMTP
 id zOrt8ykO33mD for <steve.mol...@opentext.com>;   Wed, 18 Jan 2017 
00:00:35
 + (UTC)
Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org
 [209.188.14.139])  by mx1-lw-us.apache.org (ASF Mail Server at
 mx1-lw-us.apache.org) with ESMTP id 25EFF5FE0C for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:00:35 + (UTC)
Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by
 mailrelay1-us-west.apache.org (ASF Mail Server at
 mailrelay1-us-west.apache.org) with ESMTP id BB54EE8EE5for
 <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:00:32 + (UTC)
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])by
 jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP
 id 3AF7025299  for <steve.mol...@opentext.com>; Wed, 18 Jan 2017 00:00:31
 + (UTC)
Date: Wed, 18 Jan 2017 00:00:31 +
From: "ASF subversion and git services (JIRA)" <j...@apache.org>
To: <steve.mol...@opentext.com>
Message-ID: <jira.12863036.144132000.34205.1484697631...@atlassian.jira>
In-Reply-To: <jira.12863036.144132...@atlassian.jira>
References: <jira.12863036.144132...@atlassian.jira> 
<jira.12863036.1441888832...@jira-lw-us.apache.org>
Subject: [jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs
Content-Type: text/plain; charset="utf-8"
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-CLX-Shades: None
X-CLX-Response: 1TFkXGBsSEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGxMScRsTGxAadwY 
YGgYaEQpZXhdoY2YRCklGF0VaT0ReT1JedUJFWV5PThEKQ04XRW8HU3huYk9pYnVyeXAfU2RQB3 
VJRh8SRUNufR5LXGgRClhcFx8EGgQTHAdJGRwYHhMbTgUbGgQbGxoEHhIEEhwQGx4aHxoRCl5ZF
 3pebHkFEQpNXBcYEhkRCkxaF2hpTU1TEQpMRhdsa2sRCkNaFxgaEwQbEhIEGx4EGx4YEQpCXhcb 
EQpCRhdmRFl7SHJ5QHJMTBEKQkUXYUxJa3kcZBlCH1wRCkJOF2FAQhNDU2tFZlJGEQpCTBdsBUZ 
+HRwYfU5vSBEKQmwXY15vHUB5RUgdBVARCkJAF2QBARpTeUBZfB9TEQpCWBdoTnNBTH5yWEkYfx
 EKTV4XGxEKWlgXGREKcGgXa3N4W30ZckF5X0gQGRoRCnBoF2B+T2kcbXN9WRl6EBkaEQpwaBdiG 
hgFZnxaXUF7SRAZGhEKcGgXbm0bfU54fWxSQX0QGRoRCnBoF2xreAVTHUB8fkwSEBkaEQpwfxdp 
Hl57YGV5Q2JIBRAbGRkRCnBfF2B7aRpLSFBhGE55EB4SEQpwfRdrQEZwRVJFWl1YTxAZGhEKcF8
 XZ05cAUFvXkdyGEQQHhIRCnB9F2dnWWJ8SXBIAVJlEBkaEQpwfRdmbm9OfG59QUBGTRAZGhEKcH 
8Xent/HG5fUnN+E0UQHxoRCnBfF2FvG1lJGUV5eW8fEBkaEQpwfRdkZGxfW3J4c0tsQRAZGhEKc 
GwXa15cQlxjXB8dT2sQGRoRCnBDF2NecxNnAUZselBsEBwaEQptfhcbEQpYTRdLESA=
Content-Transfer-Encoding: Quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure eng

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827091#comment-15827091
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 4d04cc85d69af51179d0ef9269b21859ed7b2861 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4d04cc8 ]

SOLR-8029: variable names changed


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821074#comment-15821074
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit e199495c4344e6c8e8861d43ab819cd451e9f1f1 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=e199495 ]

SOLR-8029: spec improvements


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821068#comment-15821068
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 09d1a8f0c00bbad82f659051acd161b523e2746e in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=09d1a8f ]

SOLR-8029: spec improvements


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821044#comment-15821044
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 5fe6090f3e42f51be8a9c164b515ffcb7fdf5835 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5fe6090 ]

SOLR-8029: spec improvements


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821037#comment-15821037
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit b1c49bc9d6287a2453ced2432fe7e008a5f8593f in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b1c49bc ]

SOLR-8029: spec improvements


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821029#comment-15821029
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit caebda946abf237a97bf844fdcc5623ee4dec2eb in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=caebda9 ]

SOLR-8029: spec improvements


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820958#comment-15820958
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit de325d98cfb86304eed299f9f794786b4bbf24a2 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=de325d9 ]

SOLR-8029: improve /_introspect support for urls with trailing variables such 
as /blob/{name}


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816355#comment-15816355
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit f1bd0f462456b4aa8273b394247c6acbadf9fa3b in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f1bd0f4 ]

SOLR-8029: added a testcase for absolute paths returned by _introspect api


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811399#comment-15811399
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 049cb10a21a4fdfa180c1931fdf901c1067f13ab in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=049cb10 ]

SOLR-8029: _introspect for per core handlers must return the full path


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15805884#comment-15805884
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit d9caa8082c0e04909fd4d6b9095464ed452742b1 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d9caa80 ]

SOLR-8029: changed command id to a parameter instead of path segment


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801527#comment-15801527
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 1fc35c136a953d8cd8ff12cfdffa328040320d73 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1fc35c1 ]

SOLR-8029: delete shard parameters added


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801033#comment-15801033
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 8c58366684f824465d46a957232664b5a11a1923 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8c58366 ]

SOLR-8029: "shard" property should be required for "split" and "create" commands


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784987#comment-15784987
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit b55e25a9900f15db1c5ffbb2f2eb1f09c831f56f in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b55e25a ]

SOLR-8029: avoid infinite loop


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15768044#comment-15768044
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 6798877180ffc136adbe70a273b3e554df8aa370 in lucene-solr's branch 
refs/heads/apiv2 from [~steve_rowe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6798877 ]

SOLR-8029: remove stray commas in api spec files


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15768045#comment-15768045
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 03eca9c111e68b74e4d9a160bcf5fb3cbc0d3ddf in lucene-solr's branch 
refs/heads/apiv2 from [~steve_rowe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=03eca9c ]

SOLR-8029: get introspect working for endpoints that don't include named cores 
or collections


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746128#comment-15746128
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 6aa57e891aca031b598c085a10d26c1d82e99343 in lucene-solr's branch 
refs/heads/apiv2 from [~steve_rowe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6aa57e8 ]

SOLR-8029: Api spec parsing: Recursively handle '#include' directives in all 
JSON objects; replace repeated analyzer definitions in the addFieldType spec 
with a single file included for each of the different types of analyzers; add 
multiTermAnalyzer key to addFieldType spec.


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735664#comment-15735664
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit cedc63d46e5aca384b8b34fbe7c51568ffbe671a in lucene-solr's branch 
refs/heads/apiv2 from [~ctargett]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=cedc63d ]

SOLR-8029: Modify schemaEdit specs; add include file for analyzers


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735663#comment-15735663
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit bf89a7a405138b39d91d4dc31a9a920e4ecf6ff3 in lucene-solr's branch 
refs/heads/apiv2 from [~ctargett]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=bf89a7a ]

SOLR-8029: Update 'cluster' specs with descriptions and links to docs


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702509#comment-15702509
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 47fd4929e60359e3df86966451ce9372dae74fd8 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=47fd492 ]

SOLR-8029: more spec refinements for schema read


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702387#comment-15702387
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 5ef717bd97cc1f479dfdf2bdd210f32406c8224d in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5ef717b ]

SOLR-8029: more spec refinements for schema edit


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702319#comment-15702319
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit f3b14aebd817e922afc0268d05a8cbbaf6b8a985 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f3b14ae ]

SOLR-8029: more spec refinements


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702289#comment-15702289
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 509db5805748e9d8e825f70058d92f6c251aa0f4 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=509db58 ]

SOLR-8029: more spec refinements


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702266#comment-15702266
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit cc21a767b92df6430cd46e2d07253ef50229c61f in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=cc21a76 ]

SOLR-8029: more spec


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702245#comment-15702245
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 5e179a18aa4bcb3697e9f4964ff2a01b9f6b082e in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5e179a1 ]

SOLR-8029: reuse add-fieldtype spec


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702022#comment-15702022
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 84695ff71f33716774b85413eced4d42fb26ad09 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=84695ff ]

SOLR-8029: add support for #include in spec files


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15698255#comment-15698255
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 16629175125ef896fa38874739f2e5d38d3cc8e3 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1662917 ]

SOLR-8029: typos


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15698254#comment-15698254
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit a919579f42123d626bc4b873325ba1ee37fec479 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=a919579 ]

SOLR-8029: refactoring


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15687216#comment-15687216
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 4942f3325e5a1f89a1902b071642163f0c806398 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4942f33 ]

SOLR-8029: cleanup code for readability


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654167#comment-15654167
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 31933ec76005f0656a5a494c18fcb3b22a8ada97 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=31933ec ]

SOLR-8029: filling in some missing specs


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654080#comment-15654080
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 776eae2449450d21b25cef0717d996cdd9b0cce3 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=776eae2 ]

SOLR-8029: filling in some missing specs


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15592703#comment-15592703
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit c482b339e7813e3b39593bda7c498ecefc547e05 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c482b33 ]

SOLR-8029: Added more details to config API


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552822#comment-15552822
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 4e879baf99b3426529e6a0f176fcfc50a1687716 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4e879ba ]

SOLR-8029: Simplified the /_introspect code and fixed a couple of bugs


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514268#comment-15514268
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit b957e2ed1f28038e6b0f07dc0f74319d89cb16c2 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b957e2e ]

SOLR-8029: testcases for configset api


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506414#comment-15506414
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 3baf6f8b3002e550400781194c4ef88a248f2ef9 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=3baf6f8 ]

SOLR-8029: more cleanup of specs. renamed collections.json 
collections.collection.json


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506132#comment-15506132
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit e0a09f5370ae770f7aeca474970969f70e30b9c8 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=e0a09f5 ]

SOLR-8029: more cleanup of specs


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15496413#comment-15496413
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit db048321565bbc2cfa92192372c782659ff21521 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=db04832 ]

SOLR-8029: cleaning up specs


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495634#comment-15495634
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit befedca2d63a1abdd7989f75d9e2af0678a2b96d in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=befedca ]

SOLR-8029:test failure addressed


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495633#comment-15495633
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 9d18a538ffb7e095a4dc1181670da7139842e5a5 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9d18a53 ]

SOLR-8029:test failure addressed


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493892#comment-15493892
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 2551c7997947f6abc7912b659ad3ceb393c3b931 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=2551c79 ]

SOLR-8029:added missing attribute


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493181#comment-15493181
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 4f53c9411eca4927f75471be5f089d5ade6c8251 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4f53c94 ]

SOLR-8029: renamed a couple of core commands and added a testcase for 
ValidatingJsonMap


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493038#comment-15493038
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit bbb44137e1f457b02f47ce0798d4d213d964d8cb in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=bbb4413 ]

SOLR-8029: moved the set-replica to collections/collection level


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492661#comment-15492661
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit c47ea512b8d483a8ccf47373ce6a6e4028a5ecca in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c47ea51 ]

SOLR-8029: balanceshardunique added


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15476890#comment-15476890
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit cf1bbc3d74fd11f81e6fa51c5c5f205fdc4e2c21 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=cf1bbc3 ]

SOLR-8029: general refactoring


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15476889#comment-15476889
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 66f09139197ce54292dc103e2d66b1b384bb79a6 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=66f0913 ]

SOLR-8029: 'enum' support in schema


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470588#comment-15470588
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit ea739f7350b0971249267532e30e979116754d2e in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ea739f7 ]

SOLR-8029: added , commands add-role, remove-role, clusterprop


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470194#comment-15470194
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit d83b6b8022d3c023344d6b1efd74e2c2f972a8c7 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d83b6b8 ]

SOLR-8029: Merge remote-tracking branch 'remotes/origin/master' into apiv2


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470193#comment-15470193
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit b49d9027b346e65853f6d1210f45d5c918760e70 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b49d902 ]

SOLR-8029: Merge remote-tracking branch 'remotes/origin/master' into apiv2


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15461475#comment-15461475
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit baec97036a2c0413830f0717f5adf1d7871b5b3c in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=baec970 ]

SOLR-8029:  more feedback from Steve addressed. ADDROLE, REMOVEROLE commands 
added


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Noble Paul (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446272#comment-15446272
 ] 

Noble Paul commented on SOLR-8029:
--



> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Noble Paul (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446274#comment-15446274
 ] 

Noble Paul commented on SOLR-8029:
--



> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Varun Thacker (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15445844#comment-15445844
 ] 

Varun Thacker commented on SOLR-8029:
-

Hi Noble,

One suggestion regarding a param in the ADDREPLICA Collections API

We currently have a param called "node" which basically can be used to tell 
Solr which node to create the replica. 
In the cluster state , the param gets stored as "node_name" . So for a user who 
calls {{CLUSTERSTATUS}} he now sees the value as "node_name" . It would be 
nicer if ADDREPLICA command renamed the param from "node" to "node_name" just 
to make it more consistent I believe.

Similarly Add Role / Delete node takes "node" as well. 

> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438801#comment-15438801
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 327aaffae4bd32df6f591a5a3c823ad19fb18df5 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=327aaff ]

SOLR-8029 : Addressing a few feedback back comments by steve. The rest to 
follow
 


*"int" is used instead of "integer" in schemas (json-schema requires 
"integer")

*  JsonSchemaValidator has no "integer" support, only "number" (e.g. no INTEGER 
in JsonSchemaValidator.Type, ApiBag.KNOWN_TYPES)

*  JsonSchemaValidator doesn't validate type values - using an invalid type 
gives an NPE instead of a useful error message

*  JsonValidatorTest is incomplete: it should test all supported schema 
validation aspects

*  Did you explore existing JSON validation libraries (instead of implementing 
from scratch)?

*  JsonSchemaValidator

*  Class javadocs should fully describe the limitations it has compared to full 
JSON schema support

*  Type.valdateData() is misspelled, should be validateData()

*  Attribute.validateData is unused, should be removed

*  Attribute class name is too vague - it could be named SchemaNode instead, 
since it represents a node in a JSON schema graph.

*  ObjectAttribute class name is too vague - it could be named SchemaAttribute 
instead, since it is a set of schema object attribute validators 

*  /url/path appears to be an orphan in many *.json files 

* These orphaned spec files should be removed:

* cores.core.Commands.requestRecovery.json (directly specified in 
cores.core.Commands.json)

* cores.json (handled by cores.Status.json)

* cluster.config.Commands.json:

* "delete" command should be removed, since that functionality is covered by 
cluster.config.delete.json

* cluster.security.RuleBasedAuthorization.json:

* /commands/delete-permission:

* "type" key is present twice - "type":"object" should be removed (since it 
should be "int")

* collections.Commands.json:

* description is spelled "Description" (capital "D") but should be lowercase

* description is a copy-paste-o:"The add-field command adds a new field 
definition to your schema."



> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Noble Paul (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15430779#comment-15430779
 ] 

Noble Paul commented on SOLR-8029:
--

Thanks [~steve_rowe] 

I shall post a detailed response after I go through all of them

> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Noble Paul (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15430026#comment-15430026
 ] 

Noble Paul commented on SOLR-8029:
--

Thanks [~arafalov] A lot of stuff that is there is the spec is not implemented 
. The scope is vast. I strongly recommend you to take a look at the branch 
{{v2api}}

bq.configset - Zookeeper only? What about for non SolrCloud installations

There is no concept of a configset outside of SolrCloud

bq.Non-distributed collection terminology - Is it still collection or core? Or 
both

The core APIs will continue to exist. So , both

bq.What's SMILE? Takes a while to find reference to some binary JSON, 

It is not added as a part of v2 API. It already exists

bq.HJSON or HOCON (misspelling or two different things?)

HJSON actually. We want to be as forgiving as possible 

bq.Operations are specified using snake case using either a dash or underscore 
- Who is making this choice? Are some operations defined one way and others the 
other?

They already exist. It is not added i V2 API

bq./v2/admin was already discussed for static resources, the spec should be 
updated if that's accepted as the solution

The spec is not a complete future plan. We have a lot of missing pieces. The 
objective is to include as much as possible and make a first release 


bq.Still talks about /solr/v2

It is {{/solr/v2}}

bq.Is Schema auto-generated from something or manually written?

It is manually written. it is a part of the source code. Please check the 
{{apiv2}} branch

A lot of stuff do not yet support schema . As of now only coponents with end 
points (request handlers ) do have schema

bq.Does the name parameter support the full Java regex or just star? If just 
star, there is no point being 'flexible' about. But if it is full regex (e.g. 
test[a-z][0-9]) , it is worth mentioning.

bq.config param - return all collections that use the specific ?collection? 

It is the same as the {{LIST}} command as of . It neither supports wild card 
nor regex. We would like to add support on both end points together

bq. With async, why are we making request to one endpoint but getting its 
status from another. 

Interesting. We should explore the semantics of supporting the same

bq.Is there no useful information to be returned when collection is created? 
Like which nodes it ends up on?

The responses are same as they are in V1 . Yes , it returns the nodes




> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Steve Rowe (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429990#comment-15429990
 ] 

Steve Rowe commented on SOLR-8029:
--

I reviewed the changes on the apiv2 branch, and found many small problems, 
which I've listed below.  I didn't attempt to prioritize them - I think they 
all should be addressed.

h3. Miscellaneous

# I couldn't find any V2 version of these old collections api actions: 
CLUSTERPROP, BALANCESHARDUNIQUE, MIGRATESTATEFORMAT, BACKUP, RESTORE, ADDROLE, 
REMOVEROLE
# Some plugins, e.g. /replication, don't have _introspect support - is this 
intentional?
# Question: I can't find it now, but I saw somewhere that only one command is 
allowed when POSTing to V2 APIs.
** Is this true?
** What about bulk schema and config APIs?  Manual V2 schema api testing with 
multiple commands in a single request resulted in all but the first command 
being silently ignored.

h3. API spec files

# There are many many many missing descriptions & documentation links, and many 
top-level CWIKI documentation links
** I think it's very important to make these as complete as possible
# Default value documentation is missing almost everywhere
** I think these should be filled in where possible
# /url/path appears to be an orphan in many *.json files - I can't find any use 
of it in code, and when it appears in *.json files, it's always a subset of 
/url/paths (plural).
# These orphaned spec files should be removed:
** cores.core.Commands.requestRecovery.json (directly specified in 
cores.core.Commands.json)
** cores.json (handled by cores.Status.json)
# Empty command properties maps, should be removed from:
** cluster.security.BasicAuth.Commands.json: /commands/set-user
** cluster.security.RuleBasedAuthorization.json: /commands/set-permission/params
# cluster.config.Commands.json:
** "delete" command should be removed, since that functionality is covered by 
cluster.config.delete.json
# cluster.security.RuleBasedAuthorization.json:
** /commands/delete-permission:
*** "type" key is present twice - "type":"object" should be removed (since it 
should be "int")
** /commands/set-user-role:
*** description should state that multiple roles should be comma-separated. 
# cluster.security.authentication.Commands.json
** Why does it contain no commands?
# cluster.security.authorization.Commands.json
** Why does it contain no commands?
# cluster.security.RuleBasedAuthorization.json: 
** "set-permission" and "update-permission" commands: required "role" property 
is never defined.
** "set-permission" command: "method" should be restricted to the allowed 
values (GET, POST, etc.)
*** JsonSchemaValidator will have to be modified to support the "enum" JSON 
schema feature
** "update-permission" command: "index" property is required, but shouldn't be, 
since "before" could be specified instead.
# collections.Commands.json:
** description is spelled "Description" (capital "D") but should be lowercase
** description is a copy-paste-o:"The add-field command adds a new field 
definition to your schema."
# core.config.Commands.json:
** type is object, no validation on the object?: most commands have this problem
*** e.g.: add-requesthandler should have required "name" and "class" (as should 
all update-* and add-* commands?)
# core.RealtimeGet.json: 
** Missing "fq" param
** How do /get/update and /get/versions work, and what do they do?  I don't see 
any code to handle them.
** /v2/c/\{collection\}/_introspect doesn't return /get/... in 
availableSubPaths, but it should
*** same problem for cores
** /v2/c/\{collection\}/get/_introspect says that the paths are /get/..., but 
that's wrong: they're /v2/c/\{collection\}/get/...
*** same problem for cores
# core.SchemaEdit.json:
** Non-supported properties that should be removed: "tokenized", "binary"
** Bulk mode doesn't work - any command after the first appears to be silently 
ignored
*** Why isn't testing failing?
** /v2/c/\{collection\}/_introspect doesn't return /schema/... in 
availableSubPaths, but it should
*** same problem for cores
** /v2/c/\{collection\}/schema/_introspect says that the paths are /schema/..., 
but that's wrong: they're /v2/c/\{collection\}/schema/...
*** same problem for cores 
# core.SchemaRead.fields.json:
** includeDynamic only applies to /schema/fields, but /schema/dynamicfields and 
/schema/fieldtypes are included in /url/paths
# cluster.json
** /v2/cluster/nodes endpoint returns same results as /v2/cluster - is 
/v2/cluster/nodes supposed to do something different?  If not, why does it need 
to be here?
# cluster.commandstatus.json
** There is no way to delete a command status (old collections api: 
DELETESTATUS action) - you can only get info on one via: GET 
/v2/cluster/command-status/\{id\}.
** Maybe this endpoint could renamed from /v2/cluster/command-status to 
/v2/cluster/async-command, and then have DELETE available on 

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[Alexandre Rafalovitch (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427381#comment-15427381
 ] 

Alexandre Rafalovitch commented on SOLR-8029:
-

I am reading the spec as a newbie, so these are comments in light of that:

h4. Solr Resources description
* core ? - we should mention/explain *core* not just mention it
* configset - Zookeeper only? What about for non SolrCloud installations
* Non-distributed collection terminology - Is it still collection or core? Or 
both

h4. Conventions
* What's SMILE? Takes a while to find reference to some binary JSON, but the 
fasterxml website was (is?) dead, maybe cross-reference JIRA we implemented it
* Query endpoints return a lot more formats (CSV, PHP, Python, HTML from 
/browse). Are those not discussed somehow? 
* HJSON or HOCON (misspelling or two different things?)
* _Endpoints that require input payloads_ - does this include "update" 
endpoint? What about XML Update format? What about /extract end point, is it 
update? Maybe clarify this a bit.
* What's an example of an _operation key_? Forward reference I guess, but hard 
to visualize this early in the document
* _Operations are specified using snake case using either a dash or underscore_ 
- Who is making this choice? Are some operations defined one way and others the 
other? Or the client call can use either? This is super-confusing and can cause 
issues to the client applications. Why can't we just have one way on this, 
since everything has to be redone anyway. 
* /v2/admin was already discussed for static resources, the spec should be 
updated if that's accepted as the solution

h4. API Versioning
* Still talks about /solr/v2

h4. Introspection support
* Is Schema auto-generated from something or manually written?
* If it is auto-generated, what is the self-description mechanism used for 
that. Because it would be good to have pluggable components (e.g. URPs, 
analysers) to self-describe themselves too, it is not clear whether that would 
be the same effort umbrella or a separate one.

h4. List collections
* Does the _name_ parameter support the full Java regex or just star? If just 
star, there is no point being 'flexible' about. But if it is full regex (e.g. 
test\[a-z\]+\[0-9\]+) , it is worth mentioning.
* _config_ param - return all collections that use the specific ?collection? 
(configset I am guessing, maybe call it configset too)

h4. Create collection
* _configTemplate_? - is that same as configset? If not, need to explain.
* With async, why are we making request to one endpoint but getting its status 
from another. That could mess a lot of users/tools up. Can we not proxy it 
internally or something. (documentation later for delete command seem to imply 
that this is already what is planned)
* Is there no useful information to be returned when collection is created? 
Like which nodes it ends up on?

h4. Collection configuration
* _sharedConfigName_ vs _configTemplate_ vs - unmentioned - _configset_ - this 
really needs to be explained in the resource description section
* Again, what happens without SolrCloud here? We are still supporting it or is 
the assumption we will not. If we will not, this needs to be documented as 
explicit precondition before merging this into master (e.g. definitely not 
version 6)

h4. Collection Alias
* Endpoint (/v2/...) is completely mismatching to the example. One of them is 
very out of date
* Earlier we said that alias is opaque to the user, which I read to say that 
call to list the collections would return aliases as well (good for tools). 
Now, it seems that they are returned in a _collection_aliases_ end point. Is 
that instead or in addition? Think about Admin UI, would we want an alias in 
the dropdown of options to run a query against (I would think yes)?
* No output seems to be shown, but will there be a marker that something is an 
alias? Or a list of collections that alias creates?
* It would make sense to have a filter that lists all aliases a collection a 
part of (it can be present in multiple I believe)

h4. Collection API and Collection Exists
* needs to be updated to use /v2/collections/collectionName structure

h4. Collection Delete
* What happens if we provide an alias name here?

h4. Swap collections?
* Do we support swapping the collections? In non-Cloud mode, obviously. And if 
we only have Cloud mode, how do we support those use-cases?

h4. Collection Administration Tasks
* Examples are all-over the place in terms of URL structure. 

h4. Link Config
* That's linking to which one of the _sharedConfigName_, _configTemplate_ or 
_configset_?
* Can reload fail? If so, would having and not having reload=true cause 
different versions of output to be present? Are there other operations that 
also need reload afterwards? This should be consistent.


h4. Share Configs
* This dual-API is super-significant for tools and Admin UI. How exactly 

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391185#comment-15391185
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 003f9b74a55d73473d8f58670f09c5abd4253c96 in lucene-solr's branch 
refs/heads/apiv2 from [~steve_rowe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=003f9b7 ]

SOLR-8029: API spec resource names: s/commands/Commands/


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387985#comment-15387985
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit f9f148fb7cf602ddefb25c6edd33887c6a93bcf0 in lucene-solr's branch 
refs/heads/apiv2 from [~steve_rowe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f9f148f ]

SOLR-8029: make precommit happy: drop unused imports and move license headers 
to the top of files


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387694#comment-15387694
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 49a09217064d6f1578895cf8425946bb2d08338d in lucene-solr's branch 
refs/heads/apiv2 from [~steve_rowe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=49a0921 ]

SOLR-8029: merge master into apiv2


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15382701#comment-15382701
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 22f1be69f9de124d15b9831e69d3ef1797160828 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=22f1be6 ]

SOLR-8029: Addressing test failures


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15382046#comment-15382046
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit 552ad6e906f8ef63b378909d9689a20955d3e1fd in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=552ad6e ]

SOLR-8029: Addressing test failures


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333651#comment-15333651
 ] 

ASF subversion and git services commented on SOLR-8029:
---

Commit b333e6bd0a3b86f85d68d47b65b12ef99ab03a86 in lucene-solr's branch 
refs/heads/apiv2 from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b333e6b ]

SOLR-8029: merging with trunk


> Modernize and standardize Solr APIs
> ---
>
> Key: SOLR-8029
> URL: https://issues.apache.org/jira/browse/SOLR-8029
> Project: Solr
>  Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Noble Paul
>Assignee: Noble Paul
>  Labels: API, EaseOfUse
> Fix For: 6.0
>
> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, 
> SOLR-8029.patch
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with 
> each other or not in sync with the widely followed conventions of HTTP 
> protocol. Trying to make incremental changes to make them modern is like 
> applying band-aid. So, we have done a complete rethink of what the APIs 
> should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy 
> APIs will continue to work under the {{/solr}} path as they used to and they 
> will be eventually deprecated.
> There are 4 types of requests in the new API 
> * {{/v2//*}} : Hit a collection directly or manage 
> collections/shards/replicas 
> * {{/v2//*}} : Hit a core directly or manage cores 
> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection 
> or core. e.g: security, overseer ops etc
> This will be released as part of a major release. Check the link given below 
> for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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