[OPT-1520] Move all type name constants from configuration to ElasticsearchConstants class Created: 10/Oct/18  Updated: 18/Apr/19  Resolved: 21/Dec/18

Status: Done
Project: Camunda Optimize
Component/s: backend
Affects Version/s: None
Fix Version/s: 2.4.0, 2.4.0-alpha1

Type: Task Priority: L3 - Default
Reporter: Johannes Heinemann Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
is related to OPT-1477 Create Optimize common library to use... Done



  • Move all Elasticsearch type and index name constants from configuration to the ElasticsearchConstants class
  • the default config file service-config.yaml also doesn't contain those entries anymore
  • the default config file in the documentation should be adjusted as well
  • Also use reference those types from the integrations tests. E.g. in the ElasticsearchIntegrationRule we have getters to retrieve the types.
  • Remove type definition from the test property files, e.g. the integration-rules.properties file

In the past we used to define all constants in the ConfigurationService, in order to allow the users to adjust the names, if they want to. However, that's actually something users don't want to do and also changes like that are not tested and very prone to error. Therefore, let's hard code all Elasticsearch type and index names in Optimize.

Generated at Tue Jun 25 03:33:10 CEST 2019 using JIRA 6.4.6#64021-sha1:33e5b454af4594f54560ac233c30a6e00459507e.