Interesting script field nuance on 0.14.2

ppearcy · January 12, 2011, 9:19pm

Hey,
0.14.2 is looking good for us, The highlighting on source cut our
indexes sizes in half, thanks!!!

One thing I noticed is that one of our custom script fields broke with
this error:
Error: statically-typed variable already defined in scope: value

The script was basically:
String value = _source[fieldName];
// Return first x number of chars from the field

I guess the value variable is now defined by ES within the scripts
execution context? Seems like an unlucky collision. My advice is for
ES to prefix all the internal variables in that scope with something
like esInternal.

The update to my script to fix is trivial and similar in the future
can be avoided by using my own prefixing on my vars.

Thanks,
Paul

ppearcy · January 12, 2011, 9:36pm

Err... I think my analysis was off base. Still looking into what my
problem is. Apologies for the noise.

On Jan 12, 2:19 pm, Paul ppea...@gmail.com wrote:

Hey,
0.14.2 is looking good for us, The highlighting on source cut our
indexes sizes in half, thanks!!!

One thing I noticed is that one of our custom script fields broke with
this error:
Error: statically-typed variable already defined in scope: value

The script was basically:
String value = _source[fieldName];
// Return first x number of chars from the field

I guess the value variable is now defined by ES within the scripts
execution context? Seems like an unlucky collision. My advice is for
ES to prefix all the internal variables in that scope with something
like esInternal.

The update to my script to fix is trivial and similar in the future
can be avoided by using my own prefixing on my vars.

Thanks,
Paul

ppearcy · January 12, 2011, 10:06pm

Not sure exactly why, but this had to do with me using a variable
within the context of a script. On 14.2 here this example fails:
scriptBuilder.append("String test = "test";");
scriptBuilder.append("return test.length();");

Don't get why, but I can work directly off the _source variable, so
that makes more sense anyways.

Thanks,
Paul

On Jan 12, 2:36 pm, Paul ppea...@gmail.com wrote:

Err... I think my analysis was off base. Still looking into what my
problem is. Apologies for the noise.

On Jan 12, 2:19 pm, Paul ppea...@gmail.com wrote:

Hey,
0.14.2 is looking good for us, The highlighting on source cut our
indexes sizes in half, thanks!!!

One thing I noticed is that one of our custom script fields broke with
this error:
Error: statically-typed variable already defined in scope: value

The script was basically:
String value = _source[fieldName];
// Return first x number of chars from the field

I guess the value variable is now defined by ES within the scripts
execution context? Seems like an unlucky collision. My advice is for
ES to prefix all the internal variables in that scope with something
like esInternal.

The update to my script to fix is trivial and similar in the future
can be avoided by using my own prefixing on my vars.

Thanks,
Paul

kimchy · January 12, 2011, 10:25pm

Can you recreate the regression with curl? I will check with mvel.
On Thursday, January 13, 2011 at 12:06 AM, Paul wrote:

Not sure exactly why, but this had to do with me using a variable
within the context of a script. On 14.2 here this example fails:
scriptBuilder.append("String test = "test";");
scriptBuilder.append("return test.length();");

Don't get why, but I can work directly off the _source variable, so
that makes more sense anyways.

Thanks,
Paul

On Jan 12, 2:36 pm, Paul ppea...@gmail.com wrote:

Err... I think my analysis was off base. Still looking into what my
problem is. Apologies for the noise.

On Jan 12, 2:19 pm, Paul ppea...@gmail.com wrote:

Hey,
0.14.2 is looking good for us, The highlighting on source cut our
indexes sizes in half, thanks!!!

One thing I noticed is that one of our custom script fields broke with
this error:
Error: statically-typed variable already defined in scope: value

The script was basically:
String value = _source[fieldName];
// Return first x number of chars from the field

I guess the value variable is now defined by ES within the scripts
execution context? Seems like an unlucky collision. My advice is for
ES to prefix all the internal variables in that scope with something
like esInternal.

The update to my script to fix is trivial and similar in the future
can be avoided by using my own prefixing on my vars.

Thanks,
Paul

ppearcy · January 19, 2011, 6:21pm

Hey Shay,
This simple example should reproduce the issue for you on 0.14.2:

gist.github.com

https://gist.github.com/ppearcy/786580

gistfile1.txt

curl -XPUT 'http://localhost:9200/twitter/'

curl -XPUT 'http://localhost:9200/twitter/tweet/1' -d '
{
    "attachmentcontent" : "test of script fields stuff"
}
'

curl -XPUT 'http://localhost:9200/twitter/tweet/2' -d '
{

This file has been truncated. show original

Thanks!

On Jan 12, 3:25 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Can you recreate the regression with curl? I will check with mvel.

On Thursday, January 13, 2011 at 12:06 AM, Paul wrote:

Not sure exactly why, but this had to do with me using a variable
within the context of a script. On 14.2 here this example fails:
scriptBuilder.append("String test = "test";");
scriptBuilder.append("return test.length();");

Don't get why, but I can work directly off the _source variable, so
that makes more sense anyways.

Thanks,
Paul

On Jan 12, 2:36 pm, Paul ppea...@gmail.com wrote:

Err... I think my analysis was off base. Still looking into what my
problem is. Apologies for the noise.

On Jan 12, 2:19 pm, Paul ppea...@gmail.com wrote:

Hey,
0.14.2 is looking good for us, The highlighting on source cut our
indexes sizes in half, thanks!!!

One thing I noticed is that one of our custom script fields broke with
this error:
Error: statically-typed variable already defined in scope: value

The script was basically:
String value = _source[fieldName];
// Return first x number of chars from the field

I guess the value variable is now defined by ES within the scripts
execution context? Seems like an unlucky collision. My advice is for
ES to prefix all the internal variables in that scope with something
like esInternal.

The update to my script to fix is trivial and similar in the future
can be avoided by using my own prefixing on my vars.

Thanks,
Paul

kimchy · January 20, 2011, 4:08pm

Can you open an issue for this? Just so I won't loose track...
On Wednesday, January 19, 2011 at 8:21 PM, Paul wrote:

Hey Shay,
This simple example should reproduce the issue for you on 0.14.2:
Script field failure · GitHub

Thanks!

On Jan 12, 3:25 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Can you recreate the regression with curl? I will check with mvel.

On Thursday, January 13, 2011 at 12:06 AM, Paul wrote:

Not sure exactly why, but this had to do with me using a variable
within the context of a script. On 14.2 here this example fails:
scriptBuilder.append("String test = "test";");
scriptBuilder.append("return test.length();");

Don't get why, but I can work directly off the _source variable, so
that makes more sense anyways.

Thanks,
Paul

On Jan 12, 2:36 pm, Paul ppea...@gmail.com wrote:

Err... I think my analysis was off base. Still looking into what my
problem is. Apologies for the noise.

On Jan 12, 2:19 pm, Paul ppea...@gmail.com wrote:

Hey,
0.14.2 is looking good for us, The highlighting on source cut our
indexes sizes in half, thanks!!!

One thing I noticed is that one of our custom script fields broke with
this error:
Error: statically-typed variable already defined in scope: value

The script was basically:
String value = _source[fieldName];
// Return first x number of chars from the field

I guess the value variable is now defined by ES within the scripts
execution context? Seems like an unlucky collision. My advice is for
ES to prefix all the internal variables in that scope with something
like esInternal.

The update to my script to fix is trivial and similar in the future
can be avoided by using my own prefixing on my vars.

Thanks,
Paul