Is it possible to retrieve index metadata via the API? In terms of
metadata, I am looking to be able to dynamically retrieve things like:
and the like.
Thanks,
Mayer
Mayer,
I do not think it is possible to get the date/time of the last time an
index was updated. Perhaps someone can prove otherwise. I would be a
bit tough in a distributed environment.
For info on the fields, you can use the mapping API:
Fields that are not explicitly defined in your initial mapping will be
added dynamically to the mapping. The GET mapping call will contain
all fields.
--
Ivan
On Thu, Dec 29, 2011 at 5:59 AM, MC mayer.crystal@gmail.com wrote:
Is it possible to retrieve index metadata via the API? In terms of
metadata, I am looking to be able to dynamically retrieve things like:
- The date/time at which an index was last updated
- The field names (currently) within an index
- The field types (string/boolean/date/numeric) currently in the
index- The field storage scheme (i.e. stored, indexed, etc...)
and the like.
Thanks,
Mayer
We manually store timestamps for creation and last update of our indices
within the "_meta" tag of a mapping. Then we use "Get Mapping" to fetch
these timestamps.
An alternative is to use the new timestamps[1] of the documents in the
index and search on that field, maybe using the term_stats facet to obtain
the max...
Hope it helps,
Philippe
[1]
On Thu, Dec 29, 2011 at 12:38, Ivan Brusic ivan@brusic.com wrote:
Mayer,
I do not think it is possible to get the date/time of the last time an
index was updated. Perhaps someone can prove otherwise. I would be a
bit tough in a distributed environment.For info on the fields, you can use the mapping API:
Elasticsearch Platform — Find real-time answers at scale | Elastic
Fields that are not explicitly defined in your initial mapping will be
added dynamically to the mapping. The GET mapping call will contain
all fields.--
IvanOn Thu, Dec 29, 2011 at 5:59 AM, MC mayer.crystal@gmail.com wrote:
Is it possible to retrieve index metadata via the API? In terms of
metadata, I am looking to be able to dynamically retrieve things like:
- The date/time at which an index was last updated
- The field names (currently) within an index
- The field types (string/boolean/date/numeric) currently in the
index- The field storage scheme (i.e. stored, indexed, etc...)
and the like.
Thanks,
Mayer
Storing the last update in the _meta part of the mapping? So does that mean
that for each document indexed, you update the mapping? Thats expensive...
On Fri, Dec 30, 2011 at 4:56 PM, Philippe Laflamme <
philippe.laflamme@obiba.org> wrote:
We manually store timestamps for creation and last update of our indices
within the "_meta" tag of a mapping. Then we use "Get Mapping" to fetch
these timestamps.An alternative is to use the new timestamps[1] of the documents in the
index and search on that field, maybe using the term_stats facet to obtain
the max...Hope it helps,
Philippe[1]
Elasticsearch Platform — Find real-time answers at scale | ElasticOn Thu, Dec 29, 2011 at 12:38, Ivan Brusic ivan@brusic.com wrote:
Mayer,
I do not think it is possible to get the date/time of the last time an
index was updated. Perhaps someone can prove otherwise. I would be a
bit tough in a distributed environment.For info on the fields, you can use the mapping API:
Elasticsearch Platform — Find real-time answers at scale | Elastic
Fields that are not explicitly defined in your initial mapping will be
added dynamically to the mapping. The GET mapping call will contain
all fields.--
IvanOn Thu, Dec 29, 2011 at 5:59 AM, MC mayer.crystal@gmail.com wrote:
Is it possible to retrieve index metadata via the API? In terms of
metadata, I am looking to be able to dynamically retrieve things like:
- The date/time at which an index was last updated
- The field names (currently) within an index
- The field types (string/boolean/date/numeric) currently in the
index- The field storage scheme (i.e. stored, indexed, etc...)
and the like.
Thanks,
Mayer
Yes, that's what we ended up with. At the time, the document timestamps
didn't exist. I wasn't aware that updating the mapping was expensive. Is
this the case even when it's not chagning at all (except under _meta)?
Philippe
On Fri, Dec 30, 2011 at 10:06, Shay Banon kimchy@gmail.com wrote:
Storing the last update in the _meta part of the mapping? So does that
mean that for each document indexed, you update the mapping? Thats
expensive...On Fri, Dec 30, 2011 at 4:56 PM, Philippe Laflamme <
philippe.laflamme@obiba.org> wrote:We manually store timestamps for creation and last update of our indices
within the "_meta" tag of a mapping. Then we use "Get Mapping" to fetch
these timestamps.An alternative is to use the new timestamps[1] of the documents in the
index and search on that field, maybe using the term_stats facet to obtain
the max...Hope it helps,
Philippe[1]
Elasticsearch Platform — Find real-time answers at scale | ElasticOn Thu, Dec 29, 2011 at 12:38, Ivan Brusic ivan@brusic.com wrote:
Mayer,
I do not think it is possible to get the date/time of the last time an
index was updated. Perhaps someone can prove otherwise. I would be a
bit tough in a distributed environment.For info on the fields, you can use the mapping API:
Elasticsearch Platform — Find real-time answers at scale | Elastic
Fields that are not explicitly defined in your initial mapping will be
added dynamically to the mapping. The GET mapping call will contain
all fields.--
IvanOn Thu, Dec 29, 2011 at 5:59 AM, MC mayer.crystal@gmail.com wrote:
Is it possible to retrieve index metadata via the API? In terms of
metadata, I am looking to be able to dynamically retrieve things like:
- The date/time at which an index was last updated
- The field names (currently) within an index
- The field types (string/boolean/date/numeric) currently in the
index- The field storage scheme (i.e. stored, indexed, etc...)
and the like.
Thanks,
Mayer
Well, expensive in the sense that it needs to be broadcasted to the cluster
and persisted (the whole metadata). Even without the timestamp feature, you
can add a timestamp to a document indexed, and find the latest one, you
don't need the timestamp to have that ability.
On Fri, Dec 30, 2011 at 6:02 PM, Philippe Laflamme <
philippe.laflamme@obiba.org> wrote:
Yes, that's what we ended up with. At the time, the document timestamps
didn't exist. I wasn't aware that updating the mapping was expensive. Is
this the case even when it's not chagning at all (except under _meta)?Philippe
On Fri, Dec 30, 2011 at 10:06, Shay Banon kimchy@gmail.com wrote:
Storing the last update in the _meta part of the mapping? So does that
mean that for each document indexed, you update the mapping? Thats
expensive...On Fri, Dec 30, 2011 at 4:56 PM, Philippe Laflamme <
philippe.laflamme@obiba.org> wrote:We manually store timestamps for creation and last update of our indices
within the "_meta" tag of a mapping. Then we use "Get Mapping" to fetch
these timestamps.An alternative is to use the new timestamps[1] of the documents in the
index and search on that field, maybe using the term_stats facet to obtain
the max...Hope it helps,
Philippe[1]
Elasticsearch Platform — Find real-time answers at scale | ElasticOn Thu, Dec 29, 2011 at 12:38, Ivan Brusic ivan@brusic.com wrote:
Mayer,
I do not think it is possible to get the date/time of the last time an
index was updated. Perhaps someone can prove otherwise. I would be a
bit tough in a distributed environment.For info on the fields, you can use the mapping API:
Elasticsearch Platform — Find real-time answers at scale | Elastic
Fields that are not explicitly defined in your initial mapping will be
added dynamically to the mapping. The GET mapping call will contain
all fields.--
IvanOn Thu, Dec 29, 2011 at 5:59 AM, MC mayer.crystal@gmail.com wrote:
Is it possible to retrieve index metadata via the API? In terms of
metadata, I am looking to be able to dynamically retrieve things like:
- The date/time at which an index was last updated
- The field names (currently) within an index
- The field types (string/boolean/date/numeric) currently in the
index- The field storage scheme (i.e. stored, indexed, etc...)
and the like.
Thanks,
Mayer
Yes, we did consider adding timestamps to documents at the time, but it
seemed more appropriate to use the _meta tag since it's an index-level
property (in our case at least). Maybe the _meta tag could be made
accessible from outside the mapping: since it's not used by es, updating it
shouldn't have any impact; just a thought.
What would be the most efficient way to query the "latest" (maximum) value
when using a timestamp field on the documents?
Thanks,
Philippe
On Fri, Dec 30, 2011 at 11:15, Shay Banon kimchy@gmail.com wrote:
Well, expensive in the sense that it needs to be broadcasted to the
cluster and persisted (the whole metadata). Even without the timestamp
feature, you can add a timestamp to a document indexed, and find the latest
one, you don't need the timestamp to have that ability.On Fri, Dec 30, 2011 at 6:02 PM, Philippe Laflamme <
philippe.laflamme@obiba.org> wrote:Yes, that's what we ended up with. At the time, the document timestamps
didn't exist. I wasn't aware that updating the mapping was expensive. Is
this the case even when it's not chagning at all (except under _meta)?Philippe
On Fri, Dec 30, 2011 at 10:06, Shay Banon kimchy@gmail.com wrote:
Storing the last update in the _meta part of the mapping? So does that
mean that for each document indexed, you update the mapping? Thats
expensive...On Fri, Dec 30, 2011 at 4:56 PM, Philippe Laflamme <
philippe.laflamme@obiba.org> wrote:We manually store timestamps for creation and last update of our
indices within the "_meta" tag of a mapping. Then we use "Get Mapping" to
fetch these timestamps.An alternative is to use the new timestamps[1] of the documents in the
index and search on that field, maybe using the term_stats facet to obtain
the max...Hope it helps,
Philippe[1]
Elasticsearch Platform — Find real-time answers at scale | ElasticOn Thu, Dec 29, 2011 at 12:38, Ivan Brusic ivan@brusic.com wrote:
Mayer,
I do not think it is possible to get the date/time of the last time an
index was updated. Perhaps someone can prove otherwise. I would be a
bit tough in a distributed environment.For info on the fields, you can use the mapping API:
Elasticsearch Platform — Find real-time answers at scale | Elastic
Fields that are not explicitly defined in your initial mapping will be
added dynamically to the mapping. The GET mapping call will contain
all fields.--
IvanOn Thu, Dec 29, 2011 at 5:59 AM, MC mayer.crystal@gmail.com wrote:
Is it possible to retrieve index metadata via the API? In terms of
metadata, I am looking to be able to dynamically retrieve things
like:
- The date/time at which an index was last updated
- The field names (currently) within an index
- The field types (string/boolean/date/numeric) currently in the
index- The field storage scheme (i.e. stored, indexed, etc...)
and the like.
Thanks,
Mayer
It does not matter if _meta is extracted or not, it still needs to be
broadcasted and persisted. The best way to get the "latest" value is to
sort base on the time field and ask for a single hit.
On Fri, Dec 30, 2011 at 6:25 PM, Philippe Laflamme <
philippe.laflamme@obiba.org> wrote:
Yes, we did consider adding timestamps to documents at the time, but it
seemed more appropriate to use the _meta tag since it's an index-level
property (in our case at least). Maybe the _meta tag could be made
accessible from outside the mapping: since it's not used by es, updating it
shouldn't have any impact; just a thought.What would be the most efficient way to query the "latest" (maximum) value
when using a timestamp field on the documents?Thanks,
PhilippeOn Fri, Dec 30, 2011 at 11:15, Shay Banon kimchy@gmail.com wrote:
Well, expensive in the sense that it needs to be broadcasted to the
cluster and persisted (the whole metadata). Even without the timestamp
feature, you can add a timestamp to a document indexed, and find the latest
one, you don't need the timestamp to have that ability.On Fri, Dec 30, 2011 at 6:02 PM, Philippe Laflamme <
philippe.laflamme@obiba.org> wrote:Yes, that's what we ended up with. At the time, the document timestamps
didn't exist. I wasn't aware that updating the mapping was expensive. Is
this the case even when it's not chagning at all (except under _meta)?Philippe
On Fri, Dec 30, 2011 at 10:06, Shay Banon kimchy@gmail.com wrote:
Storing the last update in the _meta part of the mapping? So does that
mean that for each document indexed, you update the mapping? Thats
expensive...On Fri, Dec 30, 2011 at 4:56 PM, Philippe Laflamme <
philippe.laflamme@obiba.org> wrote:We manually store timestamps for creation and last update of our
indices within the "_meta" tag of a mapping. Then we use "Get Mapping" to
fetch these timestamps.An alternative is to use the new timestamps[1] of the documents in the
index and search on that field, maybe using the term_stats facet to obtain
the max...Hope it helps,
Philippe[1]
Elasticsearch Platform — Find real-time answers at scale | ElasticOn Thu, Dec 29, 2011 at 12:38, Ivan Brusic ivan@brusic.com wrote:
Mayer,
I do not think it is possible to get the date/time of the last time an
index was updated. Perhaps someone can prove otherwise. I would be a
bit tough in a distributed environment.For info on the fields, you can use the mapping API:
Elasticsearch Platform — Find real-time answers at scale | Elastic
Fields that are not explicitly defined in your initial mapping will be
added dynamically to the mapping. The GET mapping call will contain
all fields.--
IvanOn Thu, Dec 29, 2011 at 5:59 AM, MC mayer.crystal@gmail.com wrote:
Is it possible to retrieve index metadata via the API? In terms of
metadata, I am looking to be able to dynamically retrieve things
like:
- The date/time at which an index was last updated
- The field names (currently) within an index
- The field types (string/boolean/date/numeric) currently in the
index- The field storage scheme (i.e. stored, indexed, etc...)
and the like.
Thanks,
Mayer
© 2020. All Rights Reserved - Elasticsearch
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.