Hadoop Common
  1. Hadoop Common
  2. HADOOP-6910

Replace or merge Configuration with Jakarta Commons Configuration

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Jakarta Commons Configuration: http://commons.apache.org/configuration/

        Issue Links

          Activity

          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Resolved Resolved
          1439d 2h 31m 1 Allen Wittenauer 19/Jul/14 20:13
          Allen Wittenauer made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Won't Fix [ 2 ]
          Thomas Koch made changes -
          Link This issue is related to HADOOP-5670 [ HADOOP-5670 ]
          Hide
          Luke Lu added a comment -

          Last time I checked, the commons configuration is not serializable yet (CONFIGURATION-203) and appears to be non-trivial to implement due to all its existing features and dependencies. OTOH, it's designed to have multiple backends, so a ZookeeperConfiguration (a la DatabaseConfiguration) is a natural fit

          Show
          Luke Lu added a comment - Last time I checked, the commons configuration is not serializable yet ( CONFIGURATION-203 ) and appears to be non-trivial to implement due to all its existing features and dependencies. OTOH, it's designed to have multiple backends, so a ZookeeperConfiguration (a la DatabaseConfiguration) is a natural fit
          Hide
          Allen Wittenauer added a comment -

          Is it that time of year again? HADOOP-5670

          Show
          Allen Wittenauer added a comment - Is it that time of year again? HADOOP-5670
          Hide
          Arun C Murthy added a comment -

          Not clear if Commons Config is a good fit:

          1. It doesn't seem to have have support for 'final' parameters which is critical for the server-side, we need to at least open a feature request there.
          2. Commons config doesn't seem to have support for context sensitive configs e.g. getMemory("foo", 1KB) - another feature reqeust. I believe Philip had a good proposal, I can't seem to find the jira.
          3. Commons config doesnt' seem to have support for min/max values per config knob- another feature request. Again, Philip's jira covered if I remember right.

          None of these are blockers but for support for 'final' parameters, but we need to be careful we make the switch.

          Show
          Arun C Murthy added a comment - Not clear if Commons Config is a good fit: It doesn't seem to have have support for 'final' parameters which is critical for the server-side, we need to at least open a feature request there. Commons config doesn't seem to have support for context sensitive configs e.g. getMemory("foo", 1KB) - another feature reqeust. I believe Philip had a good proposal, I can't seem to find the jira. Commons config doesnt' seem to have support for min/max values per config knob- another feature request. Again, Philip's jira covered if I remember right. None of these are blockers but for support for 'final' parameters, but we need to be careful we make the switch.
          Hide
          Owen O'Malley added a comment -

          I'm certainly not a fan of the current Configuration class, but this change seems difficult to pull off (with backwards compatibility) for pretty marginal gains.

          What are the advantages of Jakarta configurations? Can they support the current xml format or will you need to implement a new reader for them? Can it support final parameters? Are all of their configurations guaranteed to be serializable? They have a put that takes Objects, so how are those written in to XML or binary?

          Show
          Owen O'Malley added a comment - I'm certainly not a fan of the current Configuration class, but this change seems difficult to pull off (with backwards compatibility) for pretty marginal gains. What are the advantages of Jakarta configurations? Can they support the current xml format or will you need to implement a new reader for them? Can it support final parameters? Are all of their configurations guaranteed to be serializable? They have a put that takes Objects, so how are those written in to XML or binary?
          Jeff Hammerbacher made changes -
          Field Original Value New Value
          Link This issue relates to HADOOP-6909 [ HADOOP-6909 ]
          Jeff Hammerbacher created issue -

            People

            • Assignee:
              Unassigned
              Reporter:
              Jeff Hammerbacher
            • Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development