Hitachi Vantara Pentaho Community Forums
Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: creating kettle variables in javascript

  1. #1
    Brassrat Guest

    Default creating kettle variables in javascript

    The following javascript works in 2.5.
    This will no longer work in 3.0 as the kettle variable implementation
    has changed, so, how does one create kettle variables from javascript
    in 3.0?

    example javascript:
    var trans_Status= CONTINUE_TRANSFORMATION;
    var zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    var nameStr = "run.root";
    var valueStr = "/test"
    zz.setVariable(nameStr,valueStr);

    -jay


    --~--~---------~--~----~------------~-------~--~----~
    You received this message because you are subscribed to the Google Groups "kettle-developers" group.
    To post to this group, send email to kettle-developers (AT) googlegroups (DOT) com
    To unsubscribe from this group, send email to kettle-developers-unsubscribe (AT) g...oups (DOT) com
    For more options, visit this group at http://groups.google.com/group/kettle-developers?hl=en
    -~----------~----~----~----~------~----~------~--~---

  2. #2
    Sven Boden Guest

    Default Re: creating kettle variables in javascript

    For the moment not, wait a day ;-)

    Regards,
    Sven


    On Jul 27, 4:21 pm, Brassrat <jgold... (AT) vestmark (DOT) com> wrote:
    > The following javascript works in 2.5.
    > This will no longer work in 3.0 as the kettle variable implementation
    > has changed, so, how does one create kettle variables from javascript
    > in 3.0?
    >
    > example javascript:
    > var trans_Status= CONTINUE_TRANSFORMATION;
    > var zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > var nameStr = "run.root";
    > var valueStr = "/test"
    > zz.setVariable(nameStr,valueStr);
    >
    > -jay



    --~--~---------~--~----~------------~-------~--~----~
    You received this message because you are subscribed to the Google Groups "kettle-developers" group.
    To post to this group, send email to kettle-developers (AT) googlegroups (DOT) com
    To unsubscribe from this group, send email to kettle-developers-unsubscribe (AT) g...oups (DOT) com
    For more options, visit this group at http://groups.google.com/group/kettle-developers?hl=en
    -~----------~----~----~----~------~----~------~--~---

  3. #3
    Sven Boden Guest

    Default Re: creating kettle variables in javascript

    Since variables are moderately changed ;-) that snippet of code won't
    work anymore. It's also not really possible to make it backwards
    compatible, this will be the case for any use of "Package.... " when
    the implementation of the called functionality changes (inside or
    outside of Kettle).

    What I did add are 2 new functions in the modified javascript step:

    setVariable(key, value, type) and getVariable(key, default)

    The type is either "s" system-wide, "r" upto the root, "p" upto the
    parent, "g" up to the grandparent. The snippet in the original post
    has to become something as:

    var trans_Status= CONTINUE_TRANSFORMATION;
    var zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    var nameStr = "run.root";
    var valueStr = "/test"
    setVariable(nameStr,valueStr, "r");

    Regards,
    Sven


    >
    > On Jul 27, 4:21 pm, Brassrat <jgold... (AT) vestmark (DOT) com> wrote:
    >
    > > The following javascript works in 2.5.
    > > This will no longer work in 3.0 as the kettle variable implementation
    > > has changed, so, how does one create kettle variables from javascript
    > > in 3.0?

    >
    > > example javascript:
    > > var trans_Status= CONTINUE_TRANSFORMATION;
    > > var zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > > var nameStr = "run.root";
    > > var valueStr = "/test"
    > > zz.setVariable(nameStr,valueStr);

    >
    > > -jay



    --~--~---------~--~----~------------~-------~--~----~
    You received this message because you are subscribed to the Google Groups "kettle-developers" group.
    To post to this group, send email to kettle-developers (AT) googlegroups (DOT) com
    To unsubscribe from this group, send email to kettle-developers-unsubscribe (AT) g...oups (DOT) com
    For more options, visit this group at http://groups.google.com/group/kettle-developers?hl=en
    -~----------~----~----~----~------~----~------~--~---

  4. #4
    Jay Goldman Guest

    Default RE: creating kettle variables in javascript

    this sounds good ... I didn't like using the Packages... method to
    access kettle related state.

    thanks,
    jay

    -----Original Message-----
    From: kettle-developers (AT) googlegroups (DOT) com
    [mailto:kettle-developers (AT) googlegroups (DOT) com] On Behalf Of Sven Boden
    Sent: Saturday, July 28, 2007 7:00 AM
    To: kettle-developers
    Subject: Re: creating kettle variables in javascript



    Since variables are moderately changed ;-) that snippet of code won't
    work anymore. It's also not really possible to make it backwards
    compatible, this will be the case for any use of "Package.... " when the
    implementation of the called functionality changes (inside or outside of
    Kettle).

    What I did add are 2 new functions in the modified javascript step:

    setVariable(key, value, type) and getVariable(key, default)

    The type is either "s" system-wide, "r" upto the root, "p" upto the
    parent, "g" up to the grandparent. The snippet in the original post has
    to become something as:

    var trans_Status= CONTINUE_TRANSFORMATION; var
    zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    var nameStr = "run.root";
    var valueStr = "/test"
    setVariable(nameStr,valueStr, "r");

    Regards,
    Sven


    >
    > On Jul 27, 4:21 pm, Brassrat <jgold... (AT) vestmark (DOT) com> wrote:
    >
    > > The following javascript works in 2.5.
    > > This will no longer work in 3.0 as the kettle variable
    > > implementation has changed, so, how does one create kettle variables


    > > from javascript in 3.0?

    >
    > > example javascript:
    > > var trans_Status= CONTINUE_TRANSFORMATION; var
    > > zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > > var nameStr = "run.root";
    > > var valueStr = "/test"
    > > zz.setVariable(nameStr,valueStr);

    >
    > > -jay






    --~--~---------~--~----~------------~-------~--~----~
    You received this message because you are subscribed to the Google Groups "kettle-developers" group.
    To post to this group, send email to kettle-developers (AT) googlegroups (DOT) com
    To unsubscribe from this group, send email to kettle-developers-unsubscribe (AT) g...oups (DOT) com
    For more options, visit this group at http://groups.google.com/group/kettle-developers?hl=en
    -~----------~----~----~----~------~----~------~--~---

  5. #5
    Brassrat Guest

    Default Re: creating kettle variables in javascript

    btw - would it be acceptable if i added a similar function to 2.5.1 so
    i can use the same scripts for the production work i am doing?

    I am currently working on a deployment over the next month or so, so i
    can't wait for 3.0 to be ready.
    I have been testing my scripts under 3.0 to help catch any
    inconsistencies between 2.5.1 and 3.0.

    it would be nice to not have to start managing different repositories,
    etc.

    comments, please
    -jay


    On Jul 28, 11:33 am, "Jay Goldman" <jgold... (AT) vestmark (DOT) com> wrote:
    > this sounds good ... I didn't like using the Packages... method to
    > access kettle related state.
    >
    > thanks,
    > jay
    >
    > -----Original Message-----
    > From: kettle-developers (AT) googlegroups (DOT) com
    >
    > [mailto:kettle-developers (AT) googlegroups (DOT) com] On Behalf Of Sven Boden
    > Sent: Saturday, July 28, 2007 7:00 AM
    > To: kettle-developers
    > Subject: Re: creating kettle variables in javascript
    >
    > Since variables are moderately changed ;-) that snippet of code won't
    > work anymore. It's also not really possible to make it backwards
    > compatible, this will be the case for any use of "Package.... " when the
    > implementation of the called functionality changes (inside or outside of
    > Kettle).
    >
    > What I did add are 2 new functions in the modified javascript step:
    >
    > setVariable(key, value, type) and getVariable(key, default)
    >
    > The type is either "s" system-wide, "r" upto the root, "p" upto the
    > parent, "g" up to the grandparent. The snippet in the original post has
    > to become something as:
    >
    > var trans_Status= CONTINUE_TRANSFORMATION; var
    > zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > var nameStr = "run.root";
    > var valueStr = "/test"
    > setVariable(nameStr,valueStr, "r");
    >
    > Regards,
    > Sven
    >
    > > On Jul 27, 4:21 pm, Brassrat <jgold... (AT) vestmark (DOT) com> wrote:

    >
    > > > The following javascript works in 2.5.
    > > > This will no longer work in 3.0 as the kettle variable
    > > > implementation has changed, so, how does one create kettle variables

    >
    > > > from javascript in 3.0?

    >
    > > > example javascript:
    > > > var trans_Status= CONTINUE_TRANSFORMATION; var
    > > > zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > > > var nameStr = "run.root";
    > > > var valueStr = "/test"
    > > > zz.setVariable(nameStr,valueStr);

    >
    > > > -jay



    --~--~---------~--~----~------------~-------~--~----~
    You received this message because you are subscribed to the Google Groups "kettle-developers" group.
    To post to this group, send email to kettle-developers (AT) googlegroups (DOT) com
    To unsubscribe from this group, send email to kettle-developers-unsubscribe (AT) g...oups (DOT) com
    For more options, visit this group at http://groups.google.com/group/kettle-developers?hl=en
    -~----------~----~----~----~------~----~------~--~---

  6. #6
    Sven Boden Guest

    Default Re: creating kettle variables in javascript

    Personally no problem with it... although I think that you will find
    that setting the variables may give you some problems if you run using
    subjobs.

    Regards,
    Sven


    On Jul 28, 7:58 pm, Brassrat <jgold... (AT) vestmark (DOT) com> wrote:
    > btw - would it be acceptable if i added a similar function to 2.5.1 so
    > i can use the same scripts for the production work i am doing?
    >
    > I am currently working on a deployment over the next month or so, so i
    > can't wait for 3.0 to be ready.
    > I have been testing my scripts under 3.0 to help catch any
    > inconsistencies between 2.5.1 and 3.0.
    >
    > it would be nice to not have to start managing different repositories,
    > etc.
    >
    > comments, please
    > -jay
    >
    > On Jul 28, 11:33 am, "Jay Goldman" <jgold... (AT) vestmark (DOT) com> wrote:
    >
    > > this sounds good ... I didn't like using the Packages... method to
    > > access kettle related state.

    >
    > > thanks,
    > > jay

    >
    > > -----Original Message-----
    > > From: kettle-developers (AT) googlegroups (DOT) com

    >
    > > [mailto:kettle-developers (AT) googlegroups (DOT) com] On Behalf Of Sven Boden
    > > Sent: Saturday, July 28, 2007 7:00 AM
    > > To: kettle-developers
    > > Subject: Re: creating kettle variables in javascript

    >
    > > Since variables are moderately changed ;-) that snippet of code won't
    > > work anymore. It's also not really possible to make it backwards
    > > compatible, this will be the case for any use of "Package.... " when the
    > > implementation of the called functionality changes (inside or outside of
    > > Kettle).

    >
    > > What I did add are 2 new functions in the modified javascript step:

    >
    > > setVariable(key, value, type) and getVariable(key, default)

    >
    > > The type is either "s" system-wide, "r" upto the root, "p" upto the
    > > parent, "g" up to the grandparent. The snippet in the original post has
    > > to become something as:

    >
    > > var trans_Status= CONTINUE_TRANSFORMATION; var
    > > zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > > var nameStr = "run.root";
    > > var valueStr = "/test"
    > > setVariable(nameStr,valueStr, "r");

    >
    > > Regards,
    > > Sven

    >
    > > > On Jul 27, 4:21 pm, Brassrat <jgold... (AT) vestmark (DOT) com> wrote:

    >
    > > > > The following javascript works in 2.5.
    > > > > This will no longer work in 3.0 as the kettle variable
    > > > > implementation has changed, so, how does one create kettle variables

    >
    > > > > from javascript in 3.0?

    >
    > > > > example javascript:
    > > > > var trans_Status= CONTINUE_TRANSFORMATION; var
    > > > > zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > > > > var nameStr = "run.root";
    > > > > var valueStr = "/test"
    > > > > zz.setVariable(nameStr,valueStr);

    >
    > > > > -jay



    --~--~---------~--~----~------------~-------~--~----~
    You received this message because you are subscribed to the Google Groups "kettle-developers" group.
    To post to this group, send email to kettle-developers (AT) googlegroups (DOT) com
    To unsubscribe from this group, send email to kettle-developers-unsubscribe (AT) g...oups (DOT) com
    For more options, visit this group at http://groups.google.com/group/kettle-developers?hl=en
    -~----------~----~----~----~------~----~------~--~---

  7. #7
    Bruce Guest

    Default Re: creating kettle variables in javascript

    Should this be available in 3.0 M2? I tried the sample in this thread
    from Sven, but throws an error when I click the "Test script".
    The error is as follows:

    General error executing script:
    org.mozilla.javascript.EvaluatorException:
    org.mozilla.javascript.EvaluatorException: Cannot convert
    org.pentaho.di.ui.trans.steps.scriptvalues_mod.ScriptValuesModDialog
    $ScriptValuesModDummy@1b8b3bb to
    org.pentaho.di.trans.steps.scriptvalues_mod.ScriptValuesMod (script
    #5) (script #5)

    Code:
    var nameStr = "run.root";
    var valueStr = "/test"
    setVariable(nameStr,valueStr, "r");



    On Jul 28, 4:08 pm, Sven Boden <list... (AT) pandora (DOT) be> wrote:
    > Personally no problem with it... although I think that you will find
    > that setting the variables may give you some problems if you run using
    > subjobs.
    >
    > Regards,
    > Sven
    >
    > On Jul 28, 7:58 pm, Brassrat <jgold... (AT) vestmark (DOT) com> wrote:
    >
    > > btw - would it be acceptable if i added a similar function to 2.5.1 so
    > > i can use the same scripts for the production work i am doing?

    >
    > > I am currently working on a deployment over the next month or so, so i
    > > can't wait for 3.0 to be ready.
    > > I have been testing my scripts under 3.0 to help catch any
    > > inconsistencies between 2.5.1 and 3.0.

    >
    > > it would be nice to not have to start managing different repositories,
    > > etc.

    >
    > > comments, please
    > > -jay

    >
    > > On Jul 28, 11:33 am, "Jay Goldman" <jgold... (AT) vestmark (DOT) com> wrote:

    >
    > > > this sounds good ... I didn't like using the Packages... method to
    > > > access kettle related state.

    >
    > > > thanks,
    > > > jay

    >
    > > > -----Original Message-----
    > > > From: kettle-developers (AT) googlegroups (DOT) com

    >
    > > > [mailto:kettle-developers (AT) googlegroups (DOT) com] On Behalf Of Sven Boden
    > > > Sent: Saturday, July 28, 2007 7:00 AM
    > > > To: kettle-developers
    > > > Subject: Re: creating kettle variables in javascript

    >
    > > > Since variables are moderately changed ;-) that snippet of code won't
    > > > work anymore. It's also not really possible to make it backwards
    > > > compatible, this will be the case for any use of "Package.... " when the
    > > > implementation of the called functionality changes (inside or outside of
    > > > Kettle).

    >
    > > > What I did add are 2 new functions in the modified javascript step:

    >
    > > > setVariable(key, value, type) and getVariable(key, default)

    >
    > > > The type is either "s" system-wide, "r" upto the root, "p" upto the
    > > > parent, "g" up to the grandparent. The snippet in the original post has
    > > > to become something as:

    >
    > > > var trans_Status= CONTINUE_TRANSFORMATION; var
    > > > zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > > > var nameStr = "run.root";
    > > > var valueStr = "/test"
    > > > setVariable(nameStr,valueStr, "r");

    >
    > > > Regards,
    > > > Sven

    >
    > > > > On Jul 27, 4:21 pm, Brassrat <jgold... (AT) vestmark (DOT) com> wrote:

    >
    > > > > > The following javascript works in 2.5.
    > > > > > This will no longer work in 3.0 as the kettle variable
    > > > > > implementation has changed, so, how does one create kettle variables

    >
    > > > > > from javascript in 3.0?

    >
    > > > > > example javascript:
    > > > > > var trans_Status= CONTINUE_TRANSFORMATION; var
    > > > > > zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > > > > > var nameStr = "run.root";
    > > > > > var valueStr = "/test"
    > > > > > zz.setVariable(nameStr,valueStr);

    >
    > > > > > -jay



    --~--~---------~--~----~------------~-------~--~----~
    You received this message because you are subscribed to the Google Groups "kettle-developers" group.
    To post to this group, send email to kettle-developers (AT) googlegroups (DOT) com
    To unsubscribe from this group, send email to kettle-developers-unsubscribe (AT) g...oups (DOT) com
    For more options, visit this group at http://groups.google.com/group/kettle-developers?hl=en
    -~----------~----~----~----~------~----~------~--~---

  8. #8
    Sven Boden Guest

    Default Re: creating kettle variables in javascript

    Running works, test doesn't. So run, don't test for now. Test is
    always a bit tricky as some fields will be defaulted.

    Regards,
    Sven

    On Jul 28, 12:59 pm, Sven Boden <list... (AT) pandora (DOT) be> wrote:
    > Since variables are moderately changed ;-) that snippet of code won't
    > work anymore. It's also not really possible to make it backwards
    > compatible, this will be the case for any use of "Package.... " when
    > the implementation of the called functionality changes (inside or
    > outside of Kettle).
    >
    > What I did add are 2 new functions in the modified javascript step:
    >
    > setVariable(key, value, type) and getVariable(key, default)
    >
    > The type is either "s" system-wide, "r" upto the root, "p" upto the
    > parent, "g" up to the grandparent. The snippet in the original post
    > has to become something as:
    >
    > var trans_Status= CONTINUE_TRANSFORMATION;
    > var zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > var nameStr = "run.root";
    > var valueStr = "/test"
    > setVariable(nameStr,valueStr, "r");
    >
    > Regards,
    > Sven
    >
    >
    >
    > > On Jul 27, 4:21 pm, Brassrat <jgold... (AT) vestmark (DOT) com> wrote:

    >
    > > > The following javascript works in 2.5.
    > > > This will no longer work in 3.0 as the kettle variable implementation
    > > > has changed, so, how does one create kettle variables from javascript
    > > > in 3.0?

    >
    > > > example javascript:
    > > > var trans_Status= CONTINUE_TRANSFORMATION;
    > > > var zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > > > var nameStr = "run.root";
    > > > var valueStr = "/test"
    > > > zz.setVariable(nameStr,valueStr);

    >
    > > > -jay



    --~--~---------~--~----~------------~-------~--~----~
    You received this message because you are subscribed to the Google Groups "kettle-developers" group.
    To post to this group, send email to kettle-developers (AT) googlegroups (DOT) com
    To unsubscribe from this group, send email to kettle-developers-unsubscribe (AT) g...oups (DOT) com
    For more options, visit this group at http://groups.google.com/group/kettle-developers?hl=en
    -~----------~----~----~----~------~----~------~--~---

  9. #9
    Matt Casters Guest

    Default Re: creating kettle variables in javascript

    How about presenting the user with a dialog to enter the values for the used
    fields in the script(s)? You can use the current defaults.
    That way the test would be more accurate.

    Matt


    On Thursday 13 September 2007 00:17:03 Sven Boden wrote:
    > Running works, test doesn't. So run, don't test for now. Test is
    > always a bit tricky as some fields will be defaulted.
    >
    > Regards,
    > Sven
    >
    > On Jul 28, 12:59 pm, Sven Boden <list... (AT) pandora (DOT) be> wrote:
    > > Since variables are moderately changed ;-) that snippet of code won't
    > > work anymore. It's also not really possible to make it backwards
    > > compatible, this will be the case for any use of "Package.... " when
    > > the implementation of the called functionality changes (inside or
    > > outside of Kettle).
    > >
    > > What I did add are 2 new functions in the modified javascript step:
    > >
    > > setVariable(key, value, type) and getVariable(key, default)
    > >
    > > The type is either "s" system-wide, "r" upto the root, "p" upto the
    > > parent, "g" up to the grandparent. The snippet in the original post
    > > has to become something as:
    > >
    > > var trans_Status= CONTINUE_TRANSFORMATION;
    > > var zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > > var nameStr = "run.root";
    > > var valueStr = "/test"
    > > setVariable(nameStr,valueStr, "r");
    > >
    > > Regards,
    > > Sven
    > >
    > > > On Jul 27, 4:21 pm, Brassrat <jgold... (AT) vestmark (DOT) com> wrote:
    > > > > The following javascript works in 2.5.
    > > > > This will no longer work in 3.0 as the kettle variable implementation
    > > > > has changed, so, how does one create kettle variables from javascript
    > > > > in 3.0?
    > > > >
    > > > > example javascript:
    > > > > var trans_Status= CONTINUE_TRANSFORMATION;
    > > > > var zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > > > > var nameStr = "run.root";
    > > > > var valueStr = "/test"
    > > > > zz.setVariable(nameStr,valueStr);
    > > > >
    > > > > -jay

    >
    >



    --
    Matt
    ____________________________________________
    Matt Casters
    Pentaho, Open Source Business Intelligence
    http://www.pentaho.org -- mcasters (AT) pentaho (DOT) org
    Tel. +32 (0) 486 97 29 37

    --~--~---------~--~----~------------~-------~--~----~
    You received this message because you are subscribed to the Google Groups "kettle-developers" group.
    To post to this group, send email to kettle-developers (AT) googlegroups (DOT) com
    To unsubscribe from this group, send email to kettle-developers-unsubscribe (AT) g...oups (DOT) com
    For more options, visit this group at http://groups.google.com/group/kettle-developers?hl=en
    -~----------~----~----~----~------~----~------~--~---

  10. #10
    Bruce Linn Guest

    Default Re: creating kettle variables in javascript

    Thanks!

    Is there also a replacement function to handle this example?

    var value = Packages.be.ibridge.kettle.core.value.Value.getInstance();
    value.setName("fielda");
    value.setValue("valuea");
    row.addValue(value);

    -Bruce

    On 9/12/07, Sven Boden <list123 (AT) pandora (DOT) be> wrote:
    >
    >
    >
    > Running works, test doesn't. So run, don't test for now. Test is
    > always a bit tricky as some fields will be defaulted.
    >
    > Regards,
    > Sven
    >
    > On Jul 28, 12:59 pm, Sven Boden <list... (AT) pandora (DOT) be> wrote:
    > > Since variables are moderately changed ;-) that snippet of code won't
    > > work anymore. It's also not really possible to make it backwards
    > > compatible, this will be the case for any use of "Package.... " when
    > > the implementation of the called functionality changes (inside or
    > > outside of Kettle).
    > >
    > > What I did add are 2 new functions in the modified javascript step:
    > >
    > > setVariable(key, value, type) and getVariable(key, default)
    > >
    > > The type is either "s" system-wide, "r" upto the root, "p" upto the
    > > parent, "g" up to the grandparent. The snippet in the original post
    > > has to become something as:
    > >
    > > var trans_Status= CONTINUE_TRANSFORMATION;
    > > var zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance();
    > > var nameStr = "run.root";
    > > var valueStr = "/test"
    > > setVariable(nameStr,valueStr, "r");
    > >
    > > Regards,
    > > Sven
    > >
    > >
    > >
    > > > On Jul 27, 4:21 pm, Brassrat <jgold... (AT) vestmark (DOT) com> wrote:

    > >
    > > > > The following javascript works in 2.5.
    > > > > This will no longer work in 3.0 as the kettle variable

    > implementation
    > > > > has changed, so, how does one create kettle variables from

    > javascript
    > > > > in 3.0?

    > >
    > > > > example javascript:
    > > > > var trans_Status= CONTINUE_TRANSFORMATION;
    > > > > var zz=Packages.be.ibridge.kettle.core.KettleVariables.getInstance

    > ();
    > > > > var nameStr = "run.root";
    > > > > var valueStr = "/test"
    > > > > zz.setVariable(nameStr,valueStr);

    > >
    > > > > -jay

    >
    >
    > >

    >


    --~--~---------~--~----~------------~-------~--~----~
    You received this message because you are subscribed to the Google Groups "kettle-developers" group.
    To post to this group, send email to kettle-developers (AT) googlegroups (DOT) com
    To unsubscribe from this group, send email to kettle-developers-unsubscribe (AT) g...oups (DOT) com
    For more options, visit this group at http://groups.google.com/group/kettle-developers?hl=en
    -~----------~----~----~----~------~----~------~--~---

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.