[jira] [Updated] (SOLR-14829) Default components are missing facet_module and terms in documentation

2020-09-03 Thread Alexandre Rafalovitch (Jira)


 [ 
https://issues.apache.org/jira/browse/SOLR-14829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexandre Rafalovitch updated SOLR-14829:
-
Component/s: examples

> Default components are missing facet_module and terms in documentation
> --
>
> Key: SOLR-14829
> URL: https://issues.apache.org/jira/browse/SOLR-14829
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: documentation, examples
>Affects Versions: 8.6.2
>Reporter: Johannes Baiter
>Assignee: Ishan Chattopadhyaya
>Priority: Minor
> Attachments: SOLR-14829.patch
>
>
> In the reference guide, the list of search components that are enabled by 
> default is missing the {{facet_module}} and {{terms}} components. The terms 
> component is instead listed under "other useful components", while the 
> {{FacetModule}} is never listed anywhere in the documentation, despite it 
> being neccessary for the JSON Facet API to work.
> This is also how I stumbled upon this, I spent hours trying to figure out why 
> JSON-based faceting was not working with my setup, after taking a glance at 
> the {{SearchHandler}} source code based on a hunch, it became clear that my 
> custom list of search components (created based on the list in the reference 
> guide) was to blame.
> A patch for the documentation gap is attached, but I think there are some 
> other issues with the naming/documentation around the two faceting APIs that 
> may be worth discussing:
>  * The names {{facet_module}} / {{FacetModule}} are very misleading, since 
> the documentation is always talking about the "JSON Facet API", but the term 
> "JSON" does not appear in the name of the component nor does the component 
> have any documentation attached that mentions this
>  * Why is the {{FacetModule}} class located in the {{search.facet}} package 
> while every single other search component included in the core is located in 
> the {{handler.component}} package?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



[jira] [Updated] (SOLR-14829) Default components are missing facet_module and terms in documentation

2020-09-03 Thread Johannes Baiter (Jira)


 [ 
https://issues.apache.org/jira/browse/SOLR-14829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johannes Baiter updated SOLR-14829:
---
Description: 
In the reference guide, the list of search components that are enabled by 
default is missing the {{facet_module}} and {{terms}} components. The terms 
component is instead listed under "other useful components", while the 
{{FacetModule}} is never listed anywhere in the documentation, despite it being 
neccessary for the JSON Facet API to work.

This is also how I stumbled upon this, I spent hours trying to figure out why 
JSON-based faceting was not working with my setup, after taking a glance at the 
{{SearchHandler}} source code based on a hunch, it became clear that my custom 
list of search components (created based on the list in the reference guide) 
was to blame.

A patch for the documentation gap is attached, but I think there are some other 
issues with the naming/documentation around the two faceting APIs that may be 
worth discussing:
 * The names {{facet_module}} / {{FacetModule}} are very misleading, since the 
documentation is always talking about the "JSON Facet API", but the term "JSON" 
does not appear in the name of the component nor does the component have any 
documentation attached that mentions this
 * Why is the {{FacetModule}} class located in the {{search.facet}} package 
while every single other search component included in the core is located in 
the {{handler.component}} package?

  was:
In the reference guide, the list of search components that are enabled by 
default is missing the {{facet_module}} and {{terms}} components. The terms 
component is instead listed under "other useful components", while the 
{{FacetModule}} is never listed anywhere in the documentation, despite it being 
neccessary for the JSON Facet API to work.

This is also how I stumbled upon this, I spent hours trying to figure out why 
JSON-based faceting was not working with my setup, after taking a glance at the 
{{SearchHandler}} source code based on a hunch, it became clear that my custom 
list of search components (created based on the list in the reference guide) 
was to blame.

A patch for the documentation gap is attached, but I think there are some other 
issues with the naming/documentation around the two faceting APIs that may be 
worth discussing:
 * The names {{facet_module}} / {{FacetModule}} are very misleading, since the 
documentation is always talking about the "JSON Facet API", but the term "JSON" 
does not appear in the name of the component nor does the component have any 
documentation attached that mentions this
 * Why is the {{FacetModule}} class located in the {{search.facet}} package 
while every single other search component included in the core is located in 
the {{handler.component package}}?


> Default components are missing facet_module and terms in documentation
> --
>
> Key: SOLR-14829
> URL: https://issues.apache.org/jira/browse/SOLR-14829
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: documentation
>Affects Versions: 8.6.2
>Reporter: Johannes Baiter
>Priority: Minor
> Attachments: SOLR-14829.patch
>
>
> In the reference guide, the list of search components that are enabled by 
> default is missing the {{facet_module}} and {{terms}} components. The terms 
> component is instead listed under "other useful components", while the 
> {{FacetModule}} is never listed anywhere in the documentation, despite it 
> being neccessary for the JSON Facet API to work.
> This is also how I stumbled upon this, I spent hours trying to figure out why 
> JSON-based faceting was not working with my setup, after taking a glance at 
> the {{SearchHandler}} source code based on a hunch, it became clear that my 
> custom list of search components (created based on the list in the reference 
> guide) was to blame.
> A patch for the documentation gap is attached, but I think there are some 
> other issues with the naming/documentation around the two faceting APIs that 
> may be worth discussing:
>  * The names {{facet_module}} / {{FacetModule}} are very misleading, since 
> the documentation is always talking about the "JSON Facet API", but the term 
> "JSON" does not appear in the name of the component nor does the component 
> have any documentation attached that mentions this
>  * Why is the {{FacetModule}} class located in the {{search.facet}} package 
> while every single other search component included in the core is located in 
> the {{handler.component}} package?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: 

[jira] [Updated] (SOLR-14829) Default components are missing facet_module and terms in documentation

2020-09-03 Thread Johannes Baiter (Jira)


 [ 
https://issues.apache.org/jira/browse/SOLR-14829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johannes Baiter updated SOLR-14829:
---
Priority: Minor  (was: Major)

> Default components are missing facet_module and terms in documentation
> --
>
> Key: SOLR-14829
> URL: https://issues.apache.org/jira/browse/SOLR-14829
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: documentation
>Affects Versions: 8.6.2
>Reporter: Johannes Baiter
>Priority: Minor
> Attachments: SOLR-14829.patch
>
>
> In the reference guide, the list of search components that are enabled by 
> default is missing the {{facet_module}} and {{terms}} components. The terms 
> component is instead listed under "other useful components", while the 
> {{FacetModule}} is never listed anywhere in the documentation, despite it 
> being neccessary for the JSON Facet API to work.
> This is also how I stumbled upon this, I spent hours trying to figure out why 
> JSON-based faceting was not working with my setup, after taking a glance at 
> the {{SearchHandler}} source code based on a hunch, it became clear that my 
> custom list of search components (created based on the list in the reference 
> guide) was to blame.
> A patch for the documentation gap is attached, but I think there are some 
> other issues with the naming/documentation around the two faceting APIs that 
> may be worth discussing:
>  * The names {{facet_module}} / {{FacetModule}} are very misleading, since 
> the documentation is always talking about the "JSON Facet API", but the term 
> "JSON" does not appear in the name of the component nor does the component 
> have any documentation attached that mentions this
>  * Why is the {{FacetModule}} class located in the {{search.facet}} package 
> while every single other search component included in the core is located in 
> the {{handler.component package}}?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



[jira] [Updated] (SOLR-14829) Default components are missing facet_module and terms in documentation

2020-09-03 Thread Johannes Baiter (Jira)


 [ 
https://issues.apache.org/jira/browse/SOLR-14829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johannes Baiter updated SOLR-14829:
---
Description: 
In the reference guide, the list of search components that are enabled by 
default is missing the {{facet_module}} and {{terms}} components. The terms 
component is instead listed under "other useful components", while the 
{{FacetModule}} is never listed anywhere in the documentation, despite it being 
neccessary for the JSON Facet API to work.

This is also how I stumbled upon this, I spent hours trying to figure out why 
JSON-based faceting was not working with my setup, after taking a glance at the 
{{SearchHandler}} source code based on a hunch, it became clear that my custom 
list of search components (created based on the list in the reference guide) 
was to blame.

A patch for the documentation gap is attached, but I think there are some other 
issues with the naming/documentation around the two faceting APIs that may be 
worth discussing:
 * The names {{facet_module}} / {{FacetModule}} are very misleading, since the 
documentation is always talking about the "JSON Facet API", but the term "JSON" 
does not appear in the name of the component nor does the component have any 
documentation attached that mentions this
 * Why is the {{FacetModule}} class located in the {{search.facet}} package 
while every single other search component included in the core is located in 
the {{handler.component package}}?

  was:
The list of search components that are enabled by default is missing the 
{{facet_module}} and {{terms}} components. The terms component is instead 
listed under "other useful components", while the {{FacetModule}} is never 
listed anywhere in the documentation, despite it being neccessary for the JSON 
Facet API to work.

This is also how I stumbled upon this, I spent hours trying to figure out why 
JSON-based faceting was not working with my setup, after taking a glance at the 
{{SearchHandler}} source code based on a hunch, it became clear that my custom 
list of search components (created based on the list in the reference guide) 
was to blame.

A patch for the documentation gap is attached, but I think there are some other 
issues with the naming/documentation around the two faceting APIs that may be 
worth discussing:
 * The names {{facet_module}} / {{FacetModule}} are very misleading, since the 
documentation is always talking about the "JSON Facet API", but the term "JSON" 
does not appear in the name of the component nor does the component have any 
documentation attached that mentions this
 * Why is the {{FacetModule}} class located in the {{search.facet}} package 
while every single other search component included in the core is located in 
the {{handler.component package}}?


> Default components are missing facet_module and terms in documentation
> --
>
> Key: SOLR-14829
> URL: https://issues.apache.org/jira/browse/SOLR-14829
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: documentation
>Affects Versions: 8.6.2
>Reporter: Johannes Baiter
>Priority: Major
> Attachments: SOLR-14829.patch
>
>
> In the reference guide, the list of search components that are enabled by 
> default is missing the {{facet_module}} and {{terms}} components. The terms 
> component is instead listed under "other useful components", while the 
> {{FacetModule}} is never listed anywhere in the documentation, despite it 
> being neccessary for the JSON Facet API to work.
> This is also how I stumbled upon this, I spent hours trying to figure out why 
> JSON-based faceting was not working with my setup, after taking a glance at 
> the {{SearchHandler}} source code based on a hunch, it became clear that my 
> custom list of search components (created based on the list in the reference 
> guide) was to blame.
> A patch for the documentation gap is attached, but I think there are some 
> other issues with the naming/documentation around the two faceting APIs that 
> may be worth discussing:
>  * The names {{facet_module}} / {{FacetModule}} are very misleading, since 
> the documentation is always talking about the "JSON Facet API", but the term 
> "JSON" does not appear in the name of the component nor does the component 
> have any documentation attached that mentions this
>  * Why is the {{FacetModule}} class located in the {{search.facet}} package 
> while every single other search component included in the core is located in 
> the {{handler.component package}}?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For 

[jira] [Updated] (SOLR-14829) Default components are missing facet_module and terms in documentation

2020-09-03 Thread Johannes Baiter (Jira)


 [ 
https://issues.apache.org/jira/browse/SOLR-14829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johannes Baiter updated SOLR-14829:
---
Description: 
The list of search components that are enabled by default is missing the 
{{facet_module}} and {{terms}} components. The terms component is instead 
listed under "other useful components", while the {{FacetModule}} is never 
listed anywhere in the documentation, despite it being neccessary for the JSON 
Facet API to work.

This is also how I stumbled upon this, I spent hours trying to figure out why 
JSON-based faceting was not working with my setup, after taking a glance at the 
{{SearchHandler}} source code based on a hunch, it became clear that my custom 
list of search components (created based on the list in the reference guide) 
was to blame.

A patch for the documentation gap is attached, but I think there are some other 
issues with the naming/documentation around the two faceting APIs that may be 
worth discussing:
 * The names {{facet_module}} / {{FacetModule}} are very misleading, since the 
documentation is always talking about the "JSON Facet API", but the term "JSON" 
does not appear in the name of the component nor does the component have any 
documentation attached that mentions this
 * Why is the {{FacetModule}} class located in the {{search.facet}} package 
while every single other search component included in the core is located in 
the {{handler.component package}}?

  was:
The list of search components that are enabled by default is missing the 
{{facet_module}} and {{terms }}components. The terms component is instead 
listed under "other useful components", while the {{FacetModule}} is never 
listed anywhere in the documentation, despite it being neccessary for the JSON 
Facet API to work.

This is also how I stumbled upon this, I spent hours trying to figure out why 
JSON-based faceting was not working with my setup, after taking a glance at the 
{{SearchHandler}} source code based on a hunch, it became clear that my custom 
list of search components (created based on the list in the reference guide) 
was to blame.

A patch for the documentation gap is attached, but I think there are some other 
issues with the naming/documentation around the two faceting APIs that may be 
worth discussing:
 * The names {{facet_module}} / {{FacetModule}} are very misleading, since the 
documentation is always talking about the "JSON Facet API", but the term "JSON" 
does not appear in the name of the component nor does the component have any 
documentation attached that mentions this
 * Why is the {{FacetModule}} class located in the {{search.facet}} package 
while every single other search component included in the core is located in 
the {{handler.component package}}?


> Default components are missing facet_module and terms in documentation
> --
>
> Key: SOLR-14829
> URL: https://issues.apache.org/jira/browse/SOLR-14829
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: documentation
>Affects Versions: 8.6.2
>Reporter: Johannes Baiter
>Priority: Major
> Attachments: SOLR-14829.patch
>
>
> The list of search components that are enabled by default is missing the 
> {{facet_module}} and {{terms}} components. The terms component is instead 
> listed under "other useful components", while the {{FacetModule}} is never 
> listed anywhere in the documentation, despite it being neccessary for the 
> JSON Facet API to work.
> This is also how I stumbled upon this, I spent hours trying to figure out why 
> JSON-based faceting was not working with my setup, after taking a glance at 
> the {{SearchHandler}} source code based on a hunch, it became clear that my 
> custom list of search components (created based on the list in the reference 
> guide) was to blame.
> A patch for the documentation gap is attached, but I think there are some 
> other issues with the naming/documentation around the two faceting APIs that 
> may be worth discussing:
>  * The names {{facet_module}} / {{FacetModule}} are very misleading, since 
> the documentation is always talking about the "JSON Facet API", but the term 
> "JSON" does not appear in the name of the component nor does the component 
> have any documentation attached that mentions this
>  * Why is the {{FacetModule}} class located in the {{search.facet}} package 
> while every single other search component included in the core is located in 
> the {{handler.component package}}?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Updated] (SOLR-14829) Default components are missing facet_module and terms in documentation

2020-09-03 Thread Johannes Baiter (Jira)


 [ 
https://issues.apache.org/jira/browse/SOLR-14829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johannes Baiter updated SOLR-14829:
---
Attachment: SOLR-14829.patch

> Default components are missing facet_module and terms in documentation
> --
>
> Key: SOLR-14829
> URL: https://issues.apache.org/jira/browse/SOLR-14829
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: documentation
>Affects Versions: 8.6.2
>Reporter: Johannes Baiter
>Priority: Major
> Attachments: SOLR-14829.patch
>
>
> The list of search components that are enabled by default is missing the 
> {{facet_module}} and {{terms }}components. The terms component is instead 
> listed under "other useful components", while the {{FacetModule}} is never 
> listed anywhere in the documentation, despite it being neccessary for the 
> JSON Facet API to work.
> This is also how I stumbled upon this, I spent hours trying to figure out why 
> JSON-based faceting was not working with my setup, after taking a glance at 
> the {{SearchHandler}} source code based on a hunch, it became clear that my 
> custom list of search components (created based on the list in the reference 
> guide) was to blame.
> A patch for the documentation gap is attached, but I think there are some 
> other issues with the naming/documentation around the two faceting APIs that 
> may be worth discussing:
>  * The names {{facet_module}} / {{FacetModule}} are very misleading, since 
> the documentation is always talking about the "JSON Facet API", but the term 
> "JSON" does not appear in the name of the component nor does the component 
> have any documentation attached that mentions this
>  * Why is the {{FacetModule}} class located in the {{search.facet}} package 
> while every single other search component included in the core is located in 
> the {{handler.component package}}?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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