I don't think it is possible, but since parent is basically an alias for
setting the routing value you can probably use the _routing field and
related path setting along with the normal parent mapping.
Thanks for the reply.
If I set the _routing filed then the _parent filed in the source is
optional ?
-Govind
On Monday, July 29, 2013 10:56:48 AM UTC-7, Matt Weber wrote:
I don't think it is possible, but since parent is basically an alias for
setting the routing value you can probably use the _routing field and
related path setting along with the normal parent mapping.
On Mon, Jul 29, 2013 at 10:51 AM, Govind M <gov...@gmail.com <javascript:>
wrote:
By looking into the source code
org.elasticsearch.index.mapper.internal.ParentFieldMapper, it is not
possible.
Can any one confirm?
On Monday, July 29, 2013 10:44:58 AM UTC-7, Govind M wrote:
In otherwords
Can I use a "path" for the _parent field?
On Monday, July 29, 2013 9:59:08 AM UTC-7, Govind M wrote:
I would like to know if it is possible to create a mapping for parent
id to be extracted from the source, instead of specifying in the index
request.
I could see that the _id mapping is possible as below, similarly I
looking for parent id mapping
{
"tweet" : {
"_id" : {
"path" : "post_id"
}
}
}
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
Actually, now that I think about it this might since it won't set the
_parent field which I believe is used in the child id cache. I would need
to double check in the source. At any rate, you should open an issue to
support passing in the parent value via a field path during indexing.
Thanks for the reply.
If I set the _routing filed then the _parent filed in the source is
optional ?
-Govind
On Monday, July 29, 2013 10:56:48 AM UTC-7, Matt Weber wrote:
I don't think it is possible, but since parent is basically an alias for
setting the routing value you can probably use the _routing field and
related path setting along with the normal parent mapping.
On Mon, Jul 29, 2013 at 10:51 AM, Govind M gov...@gmail.com wrote:
By looking into the source code org.elasticsearch.index.**
mapper.internal.**ParentFieldMapper, it is not possible.
Can any one confirm?
On Monday, July 29, 2013 10:44:58 AM UTC-7, Govind M wrote:
In otherwords
Can I use a "path" for the _parent field?
On Monday, July 29, 2013 9:59:08 AM UTC-7, Govind M wrote:
I would like to know if it is possible to create a mapping for parent
id to be extracted from the source, instead of specifying in the index
request.
I could see that the _id mapping is possible as below, similarly I
looking for parent id mapping
{
"tweet" : {
"_id" : {
"path" : "post_id"
}
}
}
--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@**googlegroups.com.
I will certainly open an ticket for this support. Please let me know if
you find any other alternative.
On Monday, July 29, 2013 1:32:24 PM UTC-7, Matt Weber wrote:
Actually, now that I think about it this might since it won't set the
_parent field which I believe is used in the child id cache. I would need
to double check in the source. At any rate, you should open an issue to
support passing in the parent value via a field path during indexing.
Thanks,
Matt Weber
On Mon, Jul 29, 2013 at 1:02 PM, Govind M <gov...@gmail.com <javascript:>>wrote:
Hello Matt,
Thanks for the reply.
If I set the _routing filed then the _parent filed in the source is
optional ?
-Govind
On Monday, July 29, 2013 10:56:48 AM UTC-7, Matt Weber wrote:
I don't think it is possible, but since parent is basically an alias for
setting the routing value you can probably use the _routing field and
related path setting along with the normal parent mapping.
On Mon, Jul 29, 2013 at 10:51 AM, Govind M gov...@gmail.com wrote:
By looking into the source code org.elasticsearch.index.**
mapper.internal.**ParentFieldMapper, it is not possible.
Can any one confirm?
On Monday, July 29, 2013 10:44:58 AM UTC-7, Govind M wrote:
In otherwords
Can I use a "path" for the _parent field?
On Monday, July 29, 2013 9:59:08 AM UTC-7, Govind M wrote:
I would like to know if it is possible to create a mapping for parent
id to be extracted from the source, instead of specifying in the index
request.
I could see that the _id mapping is possible as below, similarly I
looking for parent id mapping
{
"tweet" : {
"_id" : {
"path" : "post_id"
}
}
}
--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@**googlegroups.com.
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
On Monday, July 29, 2013 1:53:23 PM UTC-7, Govind M wrote:
Thanks a lot Matt.
I will certainly open an ticket for this support. Please let me know if
you find any other alternative.
On Monday, July 29, 2013 1:32:24 PM UTC-7, Matt Weber wrote:
Actually, now that I think about it this might since it won't set the
_parent field which I believe is used in the child id cache. I would need
to double check in the source. At any rate, you should open an issue to
support passing in the parent value via a field path during indexing.
Thanks,
Matt Weber
On Mon, Jul 29, 2013 at 1:02 PM, Govind M gov...@gmail.com wrote:
Hello Matt,
Thanks for the reply.
If I set the _routing filed then the _parent filed in the source is
optional ?
-Govind
On Monday, July 29, 2013 10:56:48 AM UTC-7, Matt Weber wrote:
I don't think it is possible, but since parent is basically an alias
for setting the routing value you can probably use the _routing field and
related path setting along with the normal parent mapping.
On Mon, Jul 29, 2013 at 10:51 AM, Govind M gov...@gmail.com wrote:
By looking into the source code org.elasticsearch.index.**
mapper.internal.**ParentFieldMapper, it is not possible.
Can any one confirm?
On Monday, July 29, 2013 10:44:58 AM UTC-7, Govind M wrote:
In otherwords
Can I use a "path" for the _parent field?
On Monday, July 29, 2013 9:59:08 AM UTC-7, Govind M wrote:
I would like to know if it is possible to create a mapping for
parent id to be extracted from the source, instead of specifying in the
index request.
I could see that the _id mapping is possible as below, similarly I
looking for parent id mapping
{
"tweet" : {
"_id" : {
"path" : "post_id"
}
}
}
--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@**googlegroups.com.
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.