Uploaded image for project: 'Falcon'
  1. Falcon
  2. FALCON-327

Simplify message passing framework

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.5
    • 0.6
    • messaging

    Description

      Issues with the current implementation:

      • hard to evolve the schema
        If I need to add one attribute, requires change in various places
      • Too many enum classes for the same variable
        Confuses the heck out of me. Some small, some caps
      • FalconPostProcessing gets args, parses the args into CLI and converts 'em back into args repeatedly
        Too much redundant processing
      • Timestamp should be long as opposed to a String - minor?
        I need to compare dates and thought long is easier instead of constructing expensive SimpleDateFormats
      • Hard dependency on JMS.

      Suggest the following:

      • Have the payload in a Map serialized as JSON
      • wonder how to pass this from oozie
      • Have one central Enum class for the keys in the payload
      • Each class now depends on this Enum and takes what it needs from the Map

      We also could rethink about the current messaging which falcon relies on (had started a discuss thread but did not get any response):

      • Continue to use JMS
      • Switch to FS Polling
      • Use both

      Thoughts?

      Attachments

        Issue Links

          There are no Sub-Tasks for this issue.

          Activity

            People

              svenkat Venkatesh Seetharam
              svenkat Venkatesh Seetharam
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: