Details

    • Type: Sub-task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4.0, 2.4.0-alpha1
    • Component/s: backend
    • Labels:
      None

      Description

      AT:

      • the high level Elasticsearch rest client can be build from a static class in the Optimize commons package
      • the rest client is initialized in the same manner as the transport client
      • the transport client does not initialize the schema any longer
      • the schema is initialized by the rest client
      • the transport client is exposed directly instead of using a wrapper class
      • the Elasticsearch schema is initialized only once on initial startup, instead of calling it on each request
      • the Elasticsearch schema version is retrieved using the rest client

      Context:

      • The transport client will be deprecated soon and also does not work on AWS. Therefore, we need to replace it by the high level rest client.
      • In the past we supported the scenario that Optimize could be started first and then Elasticsearch and Optimize would then automatically initialize the schema. However, this scenario is not needed and makes everything very complicated. It is now required that Elasticsearch must be up running before Optimize is started. This way we only need to initialize the Schema once on the start.

        Activity

        sebastian.bathke Sebastian Bathke created issue -
        sebastian.bathke Sebastian Bathke made changes -
        Field Original Value New Value
        Rank Ranked lower
        sebastian.bathke Sebastian Bathke made changes -
        Labels current_release next_release
        sebastian.bathke Sebastian Bathke made changes -
        Labels next_release current_release next_release
        sebastian.bathke Sebastian Bathke made changes -
        Labels current_release next_release current_release
        sebastian.bathke Sebastian Bathke made changes -
        Labels current_release next_release
        johannes.heinemann Johannes Heinemann made changes -
        Labels next_release current_release next_release
        johannes.heinemann Johannes Heinemann made changes -
        Labels current_release next_release current_release
        johannes.heinemann Johannes Heinemann made changes -
        Assignee Sebastian Bathke [ sebastian.bathke ] Johannes Heinemann [ johannes.heinemann ]
        johannes.heinemann Johannes Heinemann made changes -
        Parent OPT-735 [ 37029 ]
        Issue Type Task [ 3 ] Sub-task [ 6 ]
        johannes.heinemann Johannes Heinemann made changes -
        Description currently it is called on every request from SchemaInitializingClient
        It should be enough to do this once after construction.
        *AT:*
        * the Elasticsearch

        currently it is called on every request from SchemaInitializingClient
        It should be enough to do this once after construction.
        johannes.heinemann Johannes Heinemann made changes -
        Summary Let ElasticSearchSchemaInitializer initialize the schema once on startup Use rest client to initialize Elasticsearch schema on startup
        johannes.heinemann Johannes Heinemann made changes -
        Description *AT:*
        * the Elasticsearch

        currently it is called on every request from SchemaInitializingClient
        It should be enough to do this once after construction.
        *AT:*
        * the high level Elasticsearch rest client can be build from a static class in the Optimize commons package
        * the rest client is initialized in the same manner as the transport client
        * the transport client does not initialize the schema any longer
        * the schema is initialized by the rest client
        * the transport client is exposed directly instead of using a wrapper class
        * the Elasticsearch schema is initialized only once on initial startup, instead of calling it on each request
        * the Elasticsearch schema version is retrieved using the rest client

        *Context:*
        In the past we supported
        johannes.heinemann Johannes Heinemann made changes -
        Description *AT:*
        * the high level Elasticsearch rest client can be build from a static class in the Optimize commons package
        * the rest client is initialized in the same manner as the transport client
        * the transport client does not initialize the schema any longer
        * the schema is initialized by the rest client
        * the transport client is exposed directly instead of using a wrapper class
        * the Elasticsearch schema is initialized only once on initial startup, instead of calling it on each request
        * the Elasticsearch schema version is retrieved using the rest client

        *Context:*
        In the past we supported
        *AT:*
        * the high level Elasticsearch rest client can be build from a static class in the Optimize commons package
        * the rest client is initialized in the same manner as the transport client
        * the transport client does not initialize the schema any longer
        * the schema is initialized by the rest client
        * the transport client is exposed directly instead of using a wrapper class
        * the Elasticsearch schema is initialized only once on initial startup, instead of calling it on each request
        * the Elasticsearch schema version is retrieved using the rest client

        *Context:*
        * The transport client will be deprecated soon and also does not work on AWS. Therefore, we need to replace it by the high level rest client.
        * In the past we supported the scenario that Optimize could be started first and then Elasticsearch and Optimize would then automatically initialize the schema. However, this scenario is not needed and makes everything very complicated. It is now required that Elasticsearch must be up running before Optimize is started. This way we only need to initialize the Schema once on the start.
        johannes.heinemann Johannes Heinemann made changes -
        Status Open [ 1 ] In Development [ 10312 ]
        johannes.heinemann Johannes Heinemann made changes -
        Status In Development [ 10312 ] In Review [ 10212 ]
        Assignee Johannes Heinemann [ johannes.heinemann ] Sebastian Bathke [ sebastian.bathke ]
        johannes.heinemann Johannes Heinemann made changes -
        Assignee Sebastian Bathke [ sebastian.bathke ] Johannes Heinemann [ johannes.heinemann ]
        johannes.heinemann Johannes Heinemann made changes -
        Status In Review [ 10212 ] In Specification [ 10000 ]
        johannes.heinemann Johannes Heinemann made changes -
        Status In Specification [ 10000 ] In Development [ 10312 ]
        johannes.heinemann Johannes Heinemann made changes -
        Assignee Johannes Heinemann [ johannes.heinemann ]
        Status In Development [ 10312 ] Done [ 10010 ]
        Resolution Fixed [ 1 ]
        sebastian.bathke Sebastian Bathke made changes -
        Fix Version/s 2.4.0-alpha1 [ 15369 ]
        kyrylo.zakurdaiev Kyrylo Zakurdaiev made changes -
        Labels current_release
        johannes.heinemann Johannes Heinemann made changes -
        Workflow Camunda Optimize - 2.0 [ 53858 ] Camunda Optimize - 2.4 [ 66337 ]
        sebastian.bathke Sebastian Bathke made changes -
        Fix Version/s 2.4.0 [ 15365 ]
        johannes.heinemann Johannes Heinemann made changes -
        PM Priority -1
        johannes.heinemann Johannes Heinemann made changes -
        PM Priority -1

          People

          • Assignee:
            Unassigned
            Reporter:
            sebastian.bathke Sebastian Bathke
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: