[jira] [Created] (CAMEL-18592) Re-think header naming

["Luca Burgazzoli (Jira)" <ji...@apache.org>]

Luca Burgazzoli created CAMEL-18592:
---------------------------------------

             Summary: Re-think header naming
                 Key: CAMEL-18592
                 URL: https://issues.apache.org/jira/browse/CAMEL-18592
             Project: Camel
          Issue Type: Improvement
            Reporter: Luca Burgazzoli
             Fix For: Future


As today, there is no naming convention for headers so each component is free to define them, as a result we have as example:

- CamelAwsS3BucketName
- kafka.TOPIC 

Naming is also relevant for the header filter strategy that usually remove any header that has Camel as a prefix.

We should probably define some better rules like:
- headers starting with camel.* are used to carry any camel specific attribute
- headers starting with the scheme of the component, ${scheme}.*, are meant to carry any system specific attribute
- metadata required for additional internal processing logic should be set as exchange properties (https://issues.apache.org/jira/browse/CAMEL-18591)

given the two header above, they would be translated into something like:

{code}
headers:
  aws-s3.bucket.name
  kafka.topic
properties:
  camel.aws-s3.bucket.name
{code}

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)