Just wanted to bring attention to the new and very useful transform
scripts that were introduced in elasticsearch 1.3 [1]. This feature allows
you to manipulate the source BEFORE it is indexed so you can do things like
add/remove fields, change field values, etc. Groovy scripts will be the
default, but you can write native transform scripts as well [2].
I wanted to do conditional copy_to and Andrian suggested implementing
scripted transforms instead. Much more flexible. They mesh well with the
shift to groovy too because groovy is much more stable. Stable enough to
run on every insert.
I'm glad you are excited by it. It was fun to build and I hope lots of
people enjoy it.
Just wanted to bring attention to the new and very useful transform
scripts that were introduced in elasticsearch 1.3 [1]. This feature allows
you to manipulate the source BEFORE it is indexed so you can do things like
add/remove fields, change field values, etc. Groovy scripts will be the
default, but you can write native transform scripts as well [2].
Yea, I really like it. I have been thinking about the exact same thing for
a while but never had the time to put it together. I do have some things I
would like to add such as the ability to stop a document from being indexed
when the doc has/does not have a specific value. At any rate, great job!
Thanks,
Matt Weber
On Thu, Jul 24, 2014 at 7:01 PM, Nikolas Everett nik9000@gmail.com wrote:
I wanted to do conditional copy_to and Andrian suggested implementing
scripted transforms instead. Much more flexible. They mesh well with the
shift to groovy too because groovy is much more stable. Stable enough to
run on every insert.
I'm glad you are excited by it. It was fun to build and I hope lots of
people enjoy it.
Just wanted to bring attention to the new and very useful transform
scripts that were introduced in elasticsearch 1.3 [1]. This feature allows
you to manipulate the source BEFORE it is indexed so you can do things like
add/remove fields, change field values, etc. Groovy scripts will be the
default, but you can write native transform scripts as well [2].
Yea, I really like it. I have been thinking about the exact same thing
for a while but never had the time to put it together. I do have some
things I would like to add such as the ability to stop a document from
being indexed when the doc has/does not have a specific value. At any
rate, great job!
Thanks,
Matt Weber
On Thu, Jul 24, 2014 at 7:01 PM, Nikolas Everett nik9000@gmail.com
wrote:
I wanted to do conditional copy_to and Andrian suggested implementing
scripted transforms instead. Much more flexible. They mesh well with the
shift to groovy too because groovy is much more stable. Stable enough to
run on every insert.
I'm glad you are excited by it. It was fun to build and I hope lots of
people enjoy it.
Just wanted to bring attention to the new and very useful transform
scripts that were introduced in elasticsearch 1.3 [1]. This feature allows
you to manipulate the source BEFORE it is indexed so you can do things like
add/remove fields, change field values, etc. Groovy scripts will be the
default, but you can write native transform scripts as well [2].
I have a problem i need to add dynamic fields according to certain fields value , i use groovy in simple case and it worked but the logic become more complicated and i need to separate it in external groovy script file and pass context as parameters but it didn't work and this must in mapping stage .
I have a problem i need to add dynamic fields according to certain fields
value , i use groovy in simple case and it worked but the logic become more
complicated and i need to separate it in external groovy script file and
pass context as parameters but it didn't work and this must in mapping
stage
.
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.