Re: 8.3 release

2019-10-17 Thread Shalin Shekhar Mangar
Hi Ishan, Is it okay to push https://issues.apache.org/jira/browse/SOLR-13843 to 8.3 release? The patch is ready and tested and all I need is to commit and merge it to the various branches. On Thu, Oct 17, 2019 at 4:37 AM Jan Høydahl wrote: > https://issues.apache.org/jira/browse/SOLR-13835 is

Re: [jira] [Commented] (PYLUCENE-51) "AttributeError: __module__" when running doctest

2019-10-17 Thread Andi Vajda
Added __module__ to JArray() types in rev 1868563. On Thu, 17 Oct 2019, Petrus Hyvönen (Jira) wrote: [ https://issues.apache.org/jira/browse/PYLUCENE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953958#comment-16953958 ] Petrus Hyvönen commented on

Re: [jira] [Commented] (PYLUCENE-51) "AttributeError: __module__" when running doctest

2019-10-17 Thread Andi Vajda
Ah yes, I forgot about JArray. One sec. On Thu, 17 Oct 2019, Petrus Hyvönen (Jira) wrote: [ https://issues.apache.org/jira/browse/PYLUCENE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953958#comment-16953958 ] Petrus Hyvönen commented on PYLUCENE-51:

Re: The Lucene Solr Gradle Build Game plan

2019-10-17 Thread Cassandra Targett
On Oct 17, 2019, 11:03 AM -0500, Dawid Weiss , wrote: > > I’m not sure the next steps here - we could merge the changed files into > > the main Gradle branch? > > I'm kind of waiting for Mark to coordinate this, actually. I've > modified some test code on the gradle branch but Mark has been

[jira] [Commented] (PYLUCENE-51) "AttributeError: __module__" when running doctest

2019-10-17 Thread Jira
[ https://issues.apache.org/jira/browse/PYLUCENE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953958#comment-16953958 ] Petrus Hyvönen commented on PYLUCENE-51: Many Thanks for looking into this, most classes seems

Re: Renaming SolrCloud

2019-10-17 Thread Shawn Heisey
On 10/17/2019 10:58 AM, David Smiley wrote: Some ideas: * Add a config file editor to Solr.  Not sure if our APIs are sufficient here; don't want to add another security risk. It would be VERY useful to have this. It should require explicit admin action to enable -- not enabled by default,

Re: Renaming SolrCloud

2019-10-17 Thread David Smiley
Unfortunately, I think SolrCloud / cluster mode is less easy to use than standalone mode for the developer experience locally. The main pain point is the ease of modifying configuration. In standalone, I go edit some configs using a text editor, then hit "reload" on the core. Presto. With the

Re: The Lucene Solr Gradle Build Game plan

2019-10-17 Thread Dawid Weiss
> All the targets work now - we can call this done! I've tried gradlew -p solr\solr-ref-guide buildSite buildPdf and it worked for me just fine (no syntax highlighting but I guess we can add that later). It's great to not have to install anything manually, yay. > Thank you so much Dawid for

Re: The Lucene Solr Gradle Build Game plan

2019-10-17 Thread Cassandra Targett
I’ve just pushed some changes to the "jira/SOLR-13452_gradle_7_refguide” branch - two cherry-picks from my recent changes for SOLR-12786 updating the docs for later Asciidoc versions, a couple outlier fixes I made in other commits to master I didn’t want to cherry-pick, and finally my edits to

groupingSearch does not return all the groups when using SortedSetDocValuesField

2019-10-17 Thread duriku
Hi, I managed to retrive the groups using the *SortedSetDocValuesField* in *GroupingSearch* by initialising the groupsearch with *SortedSetFieldSource* The problem is when a document has multiple values in the field "SortedSetDocValuesField" than not the grouping query does not return all the