We would like to display the following facet results:
foo (1)
One of the solution we found, is to performs a mapping using a
database query the first time the facet is processed, and then keep
the result in memory for subsequent displays.
So my question is :
Is this better to performs this on the index side (maybe by processing
a term like " foo (1)") but then, how do you achieve I18N
translations ?
Maybe an label_field (leveraging the document nature of es) option
could be helpful when submitting a facet query ?
I did not understand your use case.
Why don't you make your facet directly on categories.label ?
{
facets: { categories: { terms : { field: "categories.label" } } }
}
It should give you the results you are waiting for, should'nt it ?
We would like to display the following facet results:
foo (1)
One of the solution we found, is to performs a mapping using a
database query the first time the facet is processed, and then keep
the result in memory for subsequent displays.
So my question is :
Is this better to performs this on the index side (maybe by processing
a term like " foo (1)") but then, how do you achieve I18N
translations ?
Maybe an label_field (leveraging the document nature of es) option
could be helpful when submitting a facet query ?
you may have the same same label for two criteria (yeah i know this is weird)
Currently we have a tree of categories which contains same labels in
different parts of the tree :
ex (our tree is a bit more "leafy") :
foo
->bar
abc
->bar
I guess we can solve this problem by indexing a path of labels, and
just retrieve the last part in the view (
ex : "foo > bar".split(" > ").pop() )
Url vs labels
You may want to process url fields, instead of labels, and then just
process your view like this :
We would like to display the following facet results:
foo (1)
One of the solution we found, is to performs a mapping using a
database query the first time the facet is processed, and then keep
the result in memory for subsequent displays.
So my question is :
Is this better to performs this on the index side (maybe by processing
a term like " foo (1)") but then, how do you achieve I18N
translations ?
Maybe an label_field (leveraging the document nature of es) option
could be helpful when submitting a facet query ?
you may have the same same label for two criteria (yeah i know this is weird)
Currently we have a tree of categories which contains same labels in
different parts of the tree :
ex (our tree is a bit more "leafy") :
foo
->bar
abc
->bar
I guess we can solve this problem by indexing a path of labels, and
just retrieve the last part in the view (
ex : "foo > bar".split(" > ").pop() )
Url vs labels
You may want to process url fields, instead of labels, and then just
process your view like this :
We would like to display the following facet results:
foo (1)
One of the solution we found, is to performs a mapping using a
database query the first time the facet is processed, and then keep
the result in memory for subsequent displays.
So my question is :
Is this better to performs this on the index side (maybe by processing
a term like " foo (1)") but then, how do you achieve I18N
translations ?
Maybe an label_field (leveraging the document nature of es) option
could be helpful when submitting a facet query ?
you may have the same same label for two criteria (yeah i know this is
weird)
Currently we have a tree of categories which contains same labels in
different parts of the tree :
ex (our tree is a bit more "leafy") :
foo
->bar
abc
->bar
I guess we can solve this problem by indexing a path of labels, and
just retrieve the last part in the view (
ex : "foo > bar".split(" > ").pop() )
Url vs labels
You may want to process url fields, instead of labels, and then just
process your view like this :
We would like to display the following facet results:
foo (1)
One of the solution we found, is to performs a mapping using a
database query the first time the facet is processed, and then keep
the result in memory for subsequent displays.
So my question is :
Is this better to performs this on the index side (maybe by processing
a term like " foo (1)") but then, how do you achieve I18N
translations ?
Maybe an label_field (leveraging the document nature of es) option
could be helpful when submitting a facet query ?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.