The documents will have different keys for this as follows. These may
be fixed or varying.
'price' : {
'us' : 1.0,
'uk' : 2.0
}
My requirement, is that while querying, I need the price field as-is
by specifying
the "fields" option. In this example, I give -
fields=price
However, I get the error:
reason: "FetchPhaseExecutionException[[index_name][0]:
query[_all:a],from[0],size[10]: Fetch Failed [No mapping for field
[price]]]
Is it possible to retrieve an object, in the JSON format as is ? Or am
I doing it incorrectly ?
I do not want to retrieve the entire '_source' for getting just the
"price" fields within it.
The documents will have different keys for this as follows. These may
be fixed or varying.
'price' : {
'us' : 1.0,
'uk' : 2.0
}
My requirement, is that while querying, I need the price field as-is
by specifying
the "fields" option. In this example, I give -
fields=price
However, I get the error:
reason: "FetchPhaseExecutionException[[index_name][0]:
query[_all:a],from[0],size[10]: Fetch Failed [No mapping for field
[price]]]
Is it possible to retrieve an object, in the JSON format as is ? Or am
I doing it incorrectly ?
I do not want to retrieve the entire '_source' for getting just the
"price" fields within it.
The documents will have different keys for this as follows. These may
be fixed or varying.
'price' : {
'us' : 1.0,
'uk' : 2.0
}
My requirement, is that while querying, I need the price field as-is
by specifying
the "fields" option. In this example, I give -
fields=price
However, I get the error:
reason: "FetchPhaseExecutionException[[index_name][0]:
query[_all:a],from[0],size[10]: Fetch Failed [No mapping for field
[price]]]
Is it possible to retrieve an object, in the JSON format as is ? Or am
I doing it incorrectly ?
I do not want to retrieve the entire '_source' for getting just the
"price" fields within it.
The documents will have different keys for this as follows. These may
be fixed or varying.
'price' : {
'us' : 1.0,
'uk' : 2.0
}
My requirement, is that while querying, I need the price field as-is
by specifying
the "fields" option. In this example, I give -
fields=price
However, I get the error:
reason: "FetchPhaseExecutionException[[index_name][0]:
query[_all:a],from[0],size[10]: Fetch Failed [No mapping for field
[price]]]
Is it possible to retrieve an object, in the JSON format as is ? Or am
I doing it incorrectly ?
I do not want to retrieve the entire '_source' for getting just the
"price" fields within it.
The documents will have different keys for this as follows. These may
be fixed or varying.
'price' : {
'us' : 1.0,
'uk' : 2.0
}
My requirement, is that while querying, I need the price field as-is
by specifying
the "fields" option. In this example, I give -
fields=price
However, I get the error:
reason: "FetchPhaseExecutionException[[index_name][0]:
query[_all:a],from[0],size[10]: Fetch Failed [No mapping for field
[price]]]
Is it possible to retrieve an object, in the JSON format as is ? Or am
I doing it incorrectly ?
I do not want to retrieve the entire '_source' for getting just the
"price" fields within it.
Open an issue request, they can be added to the URI option as well. I think
that you are missing a lot of functionality by just using the search with
URI option. There shouldn't really be a problem providing a body in the
search request, no?
The documents will have different keys for this as follows. These may
be fixed or varying.
'price' : {
'us' : 1.0,
'uk' : 2.0
}
My requirement, is that while querying, I need the price field as-is
by specifying
the "fields" option. In this example, I give -
fields=price
However, I get the error:
reason: "FetchPhaseExecutionException[[index_name][0]:
query[_all:a],from[0],size[10]: Fetch Failed [No mapping for field
[price]]]
Is it possible to retrieve an object, in the JSON format as is ? Or
am
I doing it incorrectly ?
I do not want to retrieve the entire '_source' for getting just the
"price" fields within it.
Yes, I know that I am missing on quite a lot of functionality by using
just the URI option, but this is used in clients which have very
limited resources. The more powerful clients use the query API.
I have exposed the URI to very tiny embedded devices which need to
query Elasticsearch. The search URI is a simple option for them.
Another reason is, by using the "fields" API, the output of
Elasticsearch can be made very similar to the output of couchdb views.
So, clients accessing couchdb and elasticsearch can have the same
format for accessing data.
Open an issue request, they can be added to the URI option as well. I think
that you are missing a lot of functionality by just using the search with
URI option. There shouldn't really be a problem providing a body in the
search request, no?
The documents will have different keys for this as follows. These
may
be fixed or varying.
'price' : {
'us' : 1.0,
'uk' : 2.0
}
My requirement, is that while querying, I need the price field as-is
by specifying
the "fields" option. In this example, I give -
fields=price
However, I get the error:
reason: "FetchPhaseExecutionException[[index_name][0]:
query[_all:a],from[0],size[10]: Fetch Failed [No mapping for field
[price]]]
Is it possible to retrieve an object, in the JSON format as is ? Or
am
I doing it incorrectly ?
I do not want to retrieve the entire '_source' for getting just the
"price" fields within it.
The problem with using fields is that I can't tell between ones that try and
fetch a stored field, compared to script fields that will result in getting
the source... .
Yes, I know that I am missing on quite a lot of functionality by using
just the URI option, but this is used in clients which have very
limited resources. The more powerful clients use the query API.
I have exposed the URI to very tiny embedded devices which need to
query Elasticsearch. The search URI is a simple option for them.
Another reason is, by using the "fields" API, the output of
Elasticsearch can be made very similar to the output of couchdb views.
So, clients accessing couchdb and elasticsearch can have the same
format for accessing data.
Open an issue request, they can be added to the URI option as well. I
think
that you are missing a lot of functionality by just using the search with
URI option. There shouldn't really be a problem providing a body in the
search request, no?
The documents will have different keys for this as follows. These
may
be fixed or varying.
'price' : {
'us' : 1.0,
'uk' : 2.0
}
My requirement, is that while querying, I need the price field
as-is
by specifying
the "fields" option. In this example, I give -
fields=price
However, I get the error:
reason: "FetchPhaseExecutionException[[index_name][0]:
query[_all:a],from[0],size[10]: Fetch Failed [No mapping for
field
[price]]]
Is it possible to retrieve an object, in the JSON format as is ?
Or
am
I doing it incorrectly ?
I do not want to retrieve the entire '_source' for getting just
the
"price" fields within it.
The problem with using fields is that I can't tell between ones that try and
fetch a stored field, compared to script fields that will result in getting
the source... .
-shay.banon
Yes, I know that I am missing on quite a lot of functionality by using
just the URI option, but this is used in clients which have very
limited resources. The more powerful clients use the query API.
I have exposed the URI to very tiny embedded devices which need to
query Elasticsearch. The search URI is a simple option for them.
Another reason is, by using the "fields" API, the output of
Elasticsearch can be made very similar to the output of couchdb views.
So, clients accessing couchdb and elasticsearch can have the same
format for accessing data.
Open an issue request, they can be added to the URI option as well. I
think
that you are missing a lot of functionality by just using the search
with
URI option. There shouldn't really be a problem providing a body in the
search request, no?
The documents will have different keys for this as follows. These
may
be fixed or varying.
'price' : {
'us' : 1.0,
'uk' : 2.0
}
My requirement, is that while querying, I need the price field
as-is
by specifying
the "fields" option. In this example, I give -
fields=price
However, I get the error:
reason: "FetchPhaseExecutionException[[index_name][0]:
query[_all:a],from[0],size[10]: Fetch Failed [No mapping for
field
[price]]]
Is it possible to retrieve an object, in the JSON format as is ?
Or
am
I doing it incorrectly ?
I do not want to retrieve the entire '_source' for getting just
the
"price" fields within it.
The problem with using fields is that I can't tell between ones that try
and
fetch a stored field, compared to script fields that will result in
getting
the source... .
-shay.banon
Yes, I know that I am missing on quite a lot of functionality by using
just the URI option, but this is used in clients which have very
limited resources. The more powerful clients use the query API.
I have exposed the URI to very tiny embedded devices which need to
query Elasticsearch. The search URI is a simple option for them.
Another reason is, by using the "fields" API, the output of
Elasticsearch can be made very similar to the output of couchdb views.
So, clients accessing couchdb and elasticsearch can have the same
format for accessing data.
Open an issue request, they can be added to the URI option as well. I
think
that you are missing a lot of functionality by just using the search
with
URI option. There shouldn't really be a problem providing a body in
the
search request, no?
The documents will have different keys for this as follows.
These
may
be fixed or varying.
'price' : {
'us' : 1.0,
'uk' : 2.0
}
My requirement, is that while querying, I need the price field
as-is
by specifying
the "fields" option. In this example, I give -
fields=price
However, I get the error:
reason: "FetchPhaseExecutionException[[index_name][0]:
query[_all:a],from[0],size[10]: Fetch Failed [No mapping for
field
[price]]]
Is it possible to retrieve an object, in the JSON format as is
?
Or
am
I doing it incorrectly ?
I do not want to retrieve the entire '_source' for getting just
the
"price" fields within it.
The problem with using fields is that I can't tell between ones that try
and
fetch a stored field, compared to script fields that will result in
getting
the source... .
-shay.banon
Yes, I know that I am missing on quite a lot of functionality by using
just the URI option, but this is used in clients which have very
limited resources. The more powerful clients use the query API.
I have exposed the URI to very tiny embedded devices which need to
query Elasticsearch. The search URI is a simple option for them.
Another reason is, by using the "fields" API, the output of
Elasticsearch can be made very similar to the output of couchdb views.
So, clients accessing couchdb and elasticsearch can have the same
format for accessing data.
Open an issue request, they can be added to the URI option as well. I
think
that you are missing a lot of functionality by just using the search
with
URI option. There shouldn't really be a problem providing a body in
the
search request, no?
The documents will have different keys for this as follows.
These
may
be fixed or varying.
'price' : {
'us' : 1.0,
'uk' : 2.0
}
My requirement, is that while querying, I need the price field
as-is
by specifying
the "fields" option. In this example, I give -
fields=price
However, I get the error:
reason: "FetchPhaseExecutionException[[index_name][0]:
query[_all:a],from[0],size[10]: Fetch Failed [No mapping for
field
[price]]]
Is it possible to retrieve an object, in the JSON format as is
?
Or
am
I doing it incorrectly ?
I do not want to retrieve the entire '_source' for getting
just
the
"price" fields within it.
The problem with using fields is that I can't tell between ones that
try and
fetch a stored field, compared to script fields that will result in
getting
the source... .
-shay.banon
Yes, I know that I am missing on quite a lot of functionality by using
just the URI option, but this is used in clients which have very
limited resources. The more powerful clients use the query API.
I have exposed the URI to very tiny embedded devices which need to
query Elasticsearch. The search URI is a simple option for them.
Another reason is, by using the "fields" API, the output of
Elasticsearch can be made very similar to the output of couchdb views.
So, clients accessing couchdb and elasticsearch can have the same
format for accessing data.
Open an issue request, they can be added to the URI option as well.
I
think
that you are missing a lot of functionality by just using the search
with
URI option. There shouldn't really be a problem providing a body in
the
search request, no?
The documents will have different keys for this as follows.
These
may
be fixed or varying.
'price' : {
'us' : 1.0,
'uk' : 2.0
}
My requirement, is that while querying, I need the price
field
as-is
by specifying
the "fields" option. In this example, I give -
fields=price
However, I get the error:
reason: "FetchPhaseExecutionException[[index_name][0]:
query[_all:a],from[0],size[10]: Fetch Failed [No mapping
for
field
[price]]]
Is it possible to retrieve an object, in the JSON format as
is ?
Or
am
I doing it incorrectly ?
I do not want to retrieve the entire '_source' for getting
just
the
"price" fields within it.
The problem with using fields is that I can't tell between ones that
try and
fetch a stored field, compared to script fields that will result in
getting
the source... .
-shay.banon
Yes, I know that I am missing on quite a lot of functionality by using
just the URI option, but this is used in clients which have very
limited resources. The more powerful clients use the query API.
I have exposed the URI to very tiny embedded devices which need to
query Elasticsearch. The search URI is a simple option for them.
Another reason is, by using the "fields" API, the output of
Elasticsearch can be made very similar to the output of couchdb views.
So, clients accessing couchdb and elasticsearch can have the same
format for accessing data.
Open an issue request, they can be added to the URI option as well.
I
think
that you are missing a lot of functionality by just using the search
with
URI option. There shouldn't really be a problem providing a body in
the
search request, no?
The documents will have different keys for this as follows.
These
may
be fixed or varying.
'price' : {
'us' : 1.0,
'uk' : 2.0
}
My requirement, is that while querying, I need the price
field
as-is
by specifying
the "fields" option. In this example, I give -
fields=price
However, I get the error:
reason: "FetchPhaseExecutionException[[index_name][0]:
query[_all:a],from[0],size[10]: Fetch Failed [No mapping
for
field
[price]]]
Is it possible to retrieve an object, in the JSON format as
is ?
Or
am
I doing it incorrectly ?
I do not want to retrieve the entire '_source' for getting
just
the
"price" fields within it.
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.