Flume
  1. Flume
  2. FLUME-1197

Use of "timestamp" Header is hardcoded and not configurable

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Currently the HDFS sink uses the "timestamp" header to resolve the destination file path. The Syslog sources inject this header into the events for such downstream use.

      This enhancement request to change this functionality such that:

      • The header name is configurable and defaults to "flume.timestamp" to reduce collision with application namespace
      • The system still works with "timestamp" header to preserve backward compatibility.

        Activity

        Arvind Prabhakar created issue -
        Hide
        E. Sammer added a comment -

        I can see making the header configurable (although I still don't like it) but I'd prefer not to make it flume.timestamp by default. The "system provided" headers should simply be unqualified. Those that use custom headers should use their own qualified namespace.

        Show
        E. Sammer added a comment - I can see making the header configurable (although I still don't like it) but I'd prefer not to make it flume.timestamp by default. The "system provided" headers should simply be unqualified. Those that use custom headers should use their own qualified namespace.

          People

          • Assignee:
            Unassigned
            Reporter:
            Arvind Prabhakar
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development