Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33633

Change Key values to "_" vs "." as this breaks ES 2.0 and later

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • logstash-plugin
    • None

      ES 2.0 has decided it no longer wants to allow for "." in the key name. So, maybe change this to the new std of an "_" or allow us to send directly to logstash so someone can change it there using their de_dot plugin.

          [JENKINS-33633] Change Key values to "_" vs "." as this breaks ES 2.0 and later

          Rusty Gerard added a comment -

          The Logstash plugin pushes data to Elasticsearch in JSON format. Are you referring to the "denormalizing" performed by Elasticsearch, or period characters in the JSON keys?

          Rusty Gerard added a comment - The Logstash plugin pushes data to Elasticsearch in JSON format. Are you referring to the "denormalizing" performed by Elasticsearch, or period characters in the JSON keys?

          Dan K added a comment -

          Yea, so in ES > 2.0 they enforce the keys to no longer have "." in them. I think the decision was poor, but this plugin will not work going forward. So data.key1 would no longer work it would have to be data_key1

          Dan K added a comment - Yea, so in ES > 2.0 they enforce the keys to no longer have "." in them. I think the decision was poor, but this plugin will not work going forward. So data.key1 would no longer work it would have to be data_key1

          Ben Hines added a comment -

          Is this still a problem? I wanted to try out this plugin with the latest ELK.

          Ben Hines added a comment - Is this still a problem? I wanted to try out this plugin with the latest ELK.

          Russ Thompson added a comment -

          This isn't an issue for me with ElasticSearch 2.x.  Try perhaps updating your index template.

          Russ Thompson added a comment - This isn't an issue for me with ElasticSearch 2.x.  Try perhaps updating your index template.

          Jonas Bovin added a comment -

          The issue persists. If the job is a parameterised job using the run parameter. The run-parameter is a core component in Jenkins and adds variables for parameter X as X.jobName and X.jobNumber. These variables cannot be deleted once they are there. An issues was created on jenkins core in 2013, but now I doubt that after so may years they will break backwards compatibility by removing them.  

          Jonas Bovin added a comment - The issue persists. If the job is a parameterised job using the run parameter. The run-parameter is a core component in Jenkins and adds variables for parameter X as X.jobName and X.jobNumber. These variables cannot be deleted once they are there. An issues was created on jenkins core in 2013, but now I doubt that after so may years they will break backwards compatibility by removing them.  

          Faced with the same issue. Plugin 1.2, ES 2.4.

          I need to use environment variable Dcom.microsoft.tfs.jni.native.base-directory but got HTTP error 400:

          Field name [Dcom.microsoft.tfs.jni.native.base-directory] cannot contain '.'"

           

          But anyway, replacing the dot to underline isn't ok. Maybe # is a better solution. IMHO.

          ivan shevelenko added a comment - Faced with the same issue. Plugin 1.2, ES 2.4. I need to use environment variable Dcom.microsoft.tfs.jni.native.base-directory but got HTTP error 400: Field name [Dcom.microsoft.tfs.jni.native.base-directory] cannot contain '.'"   But anyway, replacing the dot to underline isn't ok. Maybe # is a better solution. IMHO.

            Unassigned Unassigned
            djtecha Dan K
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: