What is the best way to keep local state in a node in Bonobo-etl?











up vote
0
down vote

favorite
1












If I have an input queue with 20 numbers, how can I get e.g. the sum of all numbers? So far this is what I came up with:



import bonobo as bb
from bonobo.config import Configurable, ContextProcessor
from bonobo.util import ValueHolder

def extract_nums():
yield 1
yield 2
yield 3

class TransformNumber(Configurable):
@ContextProcessor
def total(self, context):
yield ValueHolder({'extract':0,'transform':0})

def __call__(self, total, num, **kwargs):
total['extract']+=num
transform_num = num * 10
total['transform']+=transform_num
if num==3: # Final number
print("TOTALS:",total.get())
yield transform_num

graph = bb.Graph()
graph.add_chain(
extract_nums,
TransformNumber(),
bb.PrettyPrinter()
)


It is ok to do it like this or is there a better way?










share|improve this question


























    up vote
    0
    down vote

    favorite
    1












    If I have an input queue with 20 numbers, how can I get e.g. the sum of all numbers? So far this is what I came up with:



    import bonobo as bb
    from bonobo.config import Configurable, ContextProcessor
    from bonobo.util import ValueHolder

    def extract_nums():
    yield 1
    yield 2
    yield 3

    class TransformNumber(Configurable):
    @ContextProcessor
    def total(self, context):
    yield ValueHolder({'extract':0,'transform':0})

    def __call__(self, total, num, **kwargs):
    total['extract']+=num
    transform_num = num * 10
    total['transform']+=transform_num
    if num==3: # Final number
    print("TOTALS:",total.get())
    yield transform_num

    graph = bb.Graph()
    graph.add_chain(
    extract_nums,
    TransformNumber(),
    bb.PrettyPrinter()
    )


    It is ok to do it like this or is there a better way?










    share|improve this question
























      up vote
      0
      down vote

      favorite
      1









      up vote
      0
      down vote

      favorite
      1






      1





      If I have an input queue with 20 numbers, how can I get e.g. the sum of all numbers? So far this is what I came up with:



      import bonobo as bb
      from bonobo.config import Configurable, ContextProcessor
      from bonobo.util import ValueHolder

      def extract_nums():
      yield 1
      yield 2
      yield 3

      class TransformNumber(Configurable):
      @ContextProcessor
      def total(self, context):
      yield ValueHolder({'extract':0,'transform':0})

      def __call__(self, total, num, **kwargs):
      total['extract']+=num
      transform_num = num * 10
      total['transform']+=transform_num
      if num==3: # Final number
      print("TOTALS:",total.get())
      yield transform_num

      graph = bb.Graph()
      graph.add_chain(
      extract_nums,
      TransformNumber(),
      bb.PrettyPrinter()
      )


      It is ok to do it like this or is there a better way?










      share|improve this question













      If I have an input queue with 20 numbers, how can I get e.g. the sum of all numbers? So far this is what I came up with:



      import bonobo as bb
      from bonobo.config import Configurable, ContextProcessor
      from bonobo.util import ValueHolder

      def extract_nums():
      yield 1
      yield 2
      yield 3

      class TransformNumber(Configurable):
      @ContextProcessor
      def total(self, context):
      yield ValueHolder({'extract':0,'transform':0})

      def __call__(self, total, num, **kwargs):
      total['extract']+=num
      transform_num = num * 10
      total['transform']+=transform_num
      if num==3: # Final number
      print("TOTALS:",total.get())
      yield transform_num

      graph = bb.Graph()
      graph.add_chain(
      extract_nums,
      TransformNumber(),
      bb.PrettyPrinter()
      )


      It is ok to do it like this or is there a better way?







      python-3.x bonobo-etl






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 8 at 17:53









      user681814

      5431517




      5431517
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote



          accepted










          There are different available options to keep local state in a Bonobo ETL node.



          It's ok to do it like you did (although I think it's hard to read), I tend to prefer to use closures which I think are more readable (but I agree, that's debatable):



          import bonobo


          def CumSum():
          total = 0

          def cum_sum(x):
          nonlocal total
          total += x
          yield x, total

          return cum_sum


          def get_graph(**options):
          graph = bonobo.Graph()
          graph.get_cursor() >> range(100) >> CumSum() >> print

          return graph


          # The __main__ block actually execute the graph.
          if __name__ == "__main__":
          parser = bonobo.get_argument_parser()
          with bonobo.parse_args(parser) as options:
          bonobo.run(get_graph(**options))


          A few examples are available in the bonobo source code, please look in https://github.com/python-bonobo/bonobo/blob/develop/bonobo/nodes/basics.py (and there are examples written in different styles).



          Note that I'm using the Bonobo 0.7 (incoming) syntax here to build the graph, but the same thing can be used with current stable version (0.6) by replacing ">>" operators by add_chain calls.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53213497%2fwhat-is-the-best-way-to-keep-local-state-in-a-node-in-bonobo-etl%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            1
            down vote



            accepted










            There are different available options to keep local state in a Bonobo ETL node.



            It's ok to do it like you did (although I think it's hard to read), I tend to prefer to use closures which I think are more readable (but I agree, that's debatable):



            import bonobo


            def CumSum():
            total = 0

            def cum_sum(x):
            nonlocal total
            total += x
            yield x, total

            return cum_sum


            def get_graph(**options):
            graph = bonobo.Graph()
            graph.get_cursor() >> range(100) >> CumSum() >> print

            return graph


            # The __main__ block actually execute the graph.
            if __name__ == "__main__":
            parser = bonobo.get_argument_parser()
            with bonobo.parse_args(parser) as options:
            bonobo.run(get_graph(**options))


            A few examples are available in the bonobo source code, please look in https://github.com/python-bonobo/bonobo/blob/develop/bonobo/nodes/basics.py (and there are examples written in different styles).



            Note that I'm using the Bonobo 0.7 (incoming) syntax here to build the graph, but the same thing can be used with current stable version (0.6) by replacing ">>" operators by add_chain calls.






            share|improve this answer

























              up vote
              1
              down vote



              accepted










              There are different available options to keep local state in a Bonobo ETL node.



              It's ok to do it like you did (although I think it's hard to read), I tend to prefer to use closures which I think are more readable (but I agree, that's debatable):



              import bonobo


              def CumSum():
              total = 0

              def cum_sum(x):
              nonlocal total
              total += x
              yield x, total

              return cum_sum


              def get_graph(**options):
              graph = bonobo.Graph()
              graph.get_cursor() >> range(100) >> CumSum() >> print

              return graph


              # The __main__ block actually execute the graph.
              if __name__ == "__main__":
              parser = bonobo.get_argument_parser()
              with bonobo.parse_args(parser) as options:
              bonobo.run(get_graph(**options))


              A few examples are available in the bonobo source code, please look in https://github.com/python-bonobo/bonobo/blob/develop/bonobo/nodes/basics.py (and there are examples written in different styles).



              Note that I'm using the Bonobo 0.7 (incoming) syntax here to build the graph, but the same thing can be used with current stable version (0.6) by replacing ">>" operators by add_chain calls.






              share|improve this answer























                up vote
                1
                down vote



                accepted







                up vote
                1
                down vote



                accepted






                There are different available options to keep local state in a Bonobo ETL node.



                It's ok to do it like you did (although I think it's hard to read), I tend to prefer to use closures which I think are more readable (but I agree, that's debatable):



                import bonobo


                def CumSum():
                total = 0

                def cum_sum(x):
                nonlocal total
                total += x
                yield x, total

                return cum_sum


                def get_graph(**options):
                graph = bonobo.Graph()
                graph.get_cursor() >> range(100) >> CumSum() >> print

                return graph


                # The __main__ block actually execute the graph.
                if __name__ == "__main__":
                parser = bonobo.get_argument_parser()
                with bonobo.parse_args(parser) as options:
                bonobo.run(get_graph(**options))


                A few examples are available in the bonobo source code, please look in https://github.com/python-bonobo/bonobo/blob/develop/bonobo/nodes/basics.py (and there are examples written in different styles).



                Note that I'm using the Bonobo 0.7 (incoming) syntax here to build the graph, but the same thing can be used with current stable version (0.6) by replacing ">>" operators by add_chain calls.






                share|improve this answer












                There are different available options to keep local state in a Bonobo ETL node.



                It's ok to do it like you did (although I think it's hard to read), I tend to prefer to use closures which I think are more readable (but I agree, that's debatable):



                import bonobo


                def CumSum():
                total = 0

                def cum_sum(x):
                nonlocal total
                total += x
                yield x, total

                return cum_sum


                def get_graph(**options):
                graph = bonobo.Graph()
                graph.get_cursor() >> range(100) >> CumSum() >> print

                return graph


                # The __main__ block actually execute the graph.
                if __name__ == "__main__":
                parser = bonobo.get_argument_parser()
                with bonobo.parse_args(parser) as options:
                bonobo.run(get_graph(**options))


                A few examples are available in the bonobo source code, please look in https://github.com/python-bonobo/bonobo/blob/develop/bonobo/nodes/basics.py (and there are examples written in different styles).



                Note that I'm using the Bonobo 0.7 (incoming) syntax here to build the graph, but the same thing can be used with current stable version (0.6) by replacing ">>" operators by add_chain calls.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 9 at 6:37









                Romain

                328212




                328212






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53213497%2fwhat-is-the-best-way-to-keep-local-state-in-a-node-in-bonobo-etl%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Guess what letter conforming each word

                    Port of Spain

                    Run scheduled task as local user group (not BUILTIN)