Hitachi Vantara Pentaho Community Forums
Results 1 to 2 of 2

Thread: Manage task properties

  1. #1
    HDupre Guest

    Default Manage task properties

    Just wondering, what would be the best way to add a property to an
    existing task without breaking existing scripts?

    I'd like to improve the xslt task to use saxon and enable xslt2
    processing.
    I see two options:
    - create a new task: ok that is fine but is there really a sense
    having multiple xslt tasks?
    - add an option to select the xsl processor: the task will then need
    specific code to check the existence of the property in the db
    properties and also in the xml...

    This is not that much of a deal but I can imagine the same problem
    raising over and over in the upcoming years... only even for our
    internal tasks.

    Also more generally for extending kettle, every task has to implement
    so low level code to load and save properties to xml and db. This is
    IMO quite heavyweight and highly bug prone. It would be really nice to
    have a higher level api to save a task's properties transparently to a
    db or an xml file for each task. I would be able to do such thing with
    xml but that can get wicked with dbs.

    Henry.


    --~--~---------~--~----~------------~-------~--~----~
    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
    Matt Casters Guest

    Default RE: Manage task properties

    Well, as far as myself is concerned that's pretty easy to answer.
    If you really think
    - that the functionality is different
    - that the existing code can't be modified to fulfill your need
    - that XLST is really needed in an ETL tool

    Then go right ahead and create a new job entry. If however the metadata is
    99% the same, don't be surprised when someone later then decides to merge
    the 2 to simplify the life of the developers.

    > highly bug prone.


    Unfortunately, the bug history disagrees with you. Please note that we are
    not preventing you in any way whatsoever to roll your own.

    As far as the simple, clean, reflection based API on top of our steps...
    Ahhh, but I think that discussion already made it into the FAQ :-)

    It's simple: this is an open source project: make a proposal, see what
    works, see what doesn't.
    Things I tried:
    - Xstream: never again, 'nough said.
    - Metadialogs, once considered/wrote a core lib to facilitate/annotate the
    link between XML/DBRep/GUI: not enough flexibility, hard to keep working,
    tricky reflection stuff, naming garbage...

    I would like to give it once more try though. I've already described what I
    think could work, I'll try to gather these thoughts in another long mail one
    of these days.
    Whatever the API or solution we can propose or try, it would have to involve
    not just XML and the repository but also the documentation and the GUI
    elements. (GUI: labels, tooltips that sort of stuff, nothing else)

    Cheers,

    Matt


    -----Original Message-----
    From: kettle-developers (AT) googlegroups (DOT) com
    [mailto:kettle-developers (AT) googlegroups (DOT) com] On Behalf Of HDupre
    Sent: Friday, May 04, 2007 12:27 AM
    To: kettle-developers
    Subject: Manage task properties


    Just wondering, what would be the best way to add a property to an existing
    task without breaking existing scripts?

    I'd like to improve the xslt task to use saxon and enable xslt2 processing.
    I see two options:
    - create a new task: ok that is fine but is there really a sense having
    multiple xslt tasks?
    - add an option to select the xsl processor: the task will then need
    specific code to check the existence of the property in the db properties
    and also in the xml...

    This is not that much of a deal but I can imagine the same problem raising
    over and over in the upcoming years... only even for our internal tasks.

    Also more generally for extending kettle, every task has to implement so low
    level code to load and save properties to xml and db. This is IMO quite
    heavyweight and highly bug prone. It would be really nice to have a higher
    level api to save a task's properties transparently to a db or an xml file
    for each task. I would be able to do such thing with xml but that can get
    wicked with dbs.

    Henry.





    --~--~---------~--~----~------------~-------~--~----~
    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.