• Type: Task
• Resolution: Fixed
• Priority: L3 - Default
• Fix Version/s: 3.12.0
• Affects Version/s: None
• Component/s: None
• Labels:

  • current_release

This is the controller panel for Smart Panels app

[OPT-7491] Implement OS DashboardWriter and DashboardReader

Ruslan Kovalenko created issue - 07/Dec/23 3:02 PM

Ruslan Kovalenko made changes - 07/Dec/23 3:02 PM

Assignee

Original: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ]

New: Ruslan Kovalenko [ ruslan.kovalenko-ext ]

Ruslan Kovalenko made changes - 07/Dec/23 3:03 PM

Status

Original: Triage [ 10612 ]

New: In Development [ 10312 ]

Giuliano Rodrigues Lima made changes - 08/Dec/23 4:54 PM

Description

Original: make the reports database agnostic

New: Do the OpenSearch implementation for the dashboard operations

Ruslan Kovalenko made changes - 11/Dec/23 10:49 AM

Assignee	Original: Ruslan Kovalenko [ ruslan.kovalenko-ext ]	New: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ]
Status	Original: In Development [ 10312 ]	New: In Review [ 10212 ]

Ruslan Kovalenko made changes - 11/Dec/23 10:49 AM

Description

Original: Do the OpenSearch implementation for the dashboard operations

New: Do the OpenSearch implementation for the dashboard operations *Testing notes* Implemented ReportWriterOS and ReportReaderOS should add 3 records at the single-report-index while launching the app with os db profile. The content of these records should be the same as we have while launching the app with es db profile.  To make this process easier I would advice to set up the chrome extension *Multi Elasticsearch Head* and connect to the elasticsearch(9200 port) and opensearch(9205 port) after launching the app 2 times with the different db profiles. Then find the tab "Browse" and open indices to see the content of them. Then compare.  To launch the app you have to with opensearch db profile:  # Run  {code:java} docker-compose -f docker-compose.yml --profile opensearch up -d{code}  # Start Optimize with  {code:java} SPRING_PROFILES_ACTIVE=opensearch{code}  # The startup will fail and that's ok, BUT...  # Check that all indexes were created in opensearch  # Then go to the tab with chrome extension

Ruslan Kovalenko made changes - 11/Dec/23 10:50 AM

Description

Original: Do the OpenSearch implementation for the dashboard operations *Testing notes* Implemented ReportWriterOS and ReportReaderOS should add 3 records at the single-report-index while launching the app with os db profile. The content of these records should be the same as we have while launching the app with es db profile.  To make this process easier I would advice to set up the chrome extension *Multi Elasticsearch Head* and connect to the elasticsearch(9200 port) and opensearch(9205 port) after launching the app 2 times with the different db profiles. Then find the tab "Browse" and open indices to see the content of them. Then compare.  To launch the app you have to with opensearch db profile:  # Run  {code:java} docker-compose -f docker-compose.yml --profile opensearch up -d{code}  # Start Optimize with  {code:java} SPRING_PROFILES_ACTIVE=opensearch{code}  # The startup will fail and that's ok, BUT...  # Check that all indexes were created in opensearch  # Then go to the tab with chrome extension

New: Do the OpenSearch implementation for the dashboard operations *Testing notes* Implemented DashboardWriterOS and DashboardReaderOS should add 1 record at the optimize-dashboard-v8 while launching the app with os db profile. The content of these records should be the same as we have while launching the app with es db profile.  To make this process easier I would advice to set up the chrome extension *Multi Elasticsearch Head* and connect to the elasticsearch(9200 port) and opensearch(9205 port) after launching the app 2 times with the different db profiles. Then find the tab "Browse" and open indices to see the content of them. Then compare.  To launch the app you have to with opensearch db profile:  # Run  {code:java} docker-compose -f docker-compose.yml --profile opensearch up -d{code}  # Start Optimize with  {code:java} SPRING_PROFILES_ACTIVE=opensearch{code}  # The startup will fail and that's ok, BUT...  # Check that all indexes were created in opensearch  # Then go to the tab with chrome extension

Giuliano Rodrigues Lima made changes - 13/Dec/23 1:36 PM

Assignee	Original: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ]	New: Ruslan Kovalenko [ ruslan.kovalenko-ext ]
Status	Original: In Review [ 10212 ]	New: Rework [ 11413 ]

Giuliano Rodrigues Lima made changes - 14/Dec/23 9:26 AM

Assignee	Original: Ruslan Kovalenko [ ruslan.kovalenko-ext ]	New: Cigdem Ilhan [ cigdem.ilhan ]
Status	Original: Rework [ 11413 ]	New: Ready for Testing [ 10008 ]

Cigdem Ilhan made changes - 15/Dec/23 1:59 PM

Fix Version/s

New: 3.12.0 [ 18790 ]

Load more newer events