Setting the dual query parameters for the old data

After the upgrade to 1.4.6, some data that is stored in DiamondDB might not be visible. Update the specific parameters in the Timeseries Service YAML file to ensure that the data is retrieved from both DiamondDB and Timeseries Services.

1. Log in to your cloud platform web console on your primary cluster.
2. Expand Workloads > Stateful Sets > timeseries.
3. 
   Click the YAML tab.
   Add the parameters to the Timeseries Stateful Set YAML file in the args: section. The following parameter is existing in the YAML file.

   - '--timeseries.pre-agg.meta.path=/opt/basecamp/timeseries/data'

   Add the new parameters as follows:

   - '--database.read.url=diamonddb://diamond-db-read:30110'
   - '--timeseries.diamond.export.url=diamonddb://diamond-db-export:30120'
   - '--old.database.cutoffInMs=<Time of upgrade in Epoch format>'

   The value for the old.database.cutoffs parameter must be the day that you completed the upgrade with time as 12 midnight in Epoch time format.

   For example, if the date is 18th, June 2023, its Epoch timestamp in milliseconds is 1687046400000.

   The timeseries-0 Pod is restarted automatically.

4. 
   Click the Edit resource icon ().
5. Add the parameters to the Timeseries Stateful Set YAML file in the args: section. The following parameter is existing in the YAML file.

   - '--timeseries.pre-agg.meta.path=/opt/basecamp/timeseries/data'

   Add the new parameters as follows:

   - '--database.read.url=diamonddb://diamond-db-read:30110'
   - '--timeseries.diamond.export.url=diamonddb://diamond-db-export:30120'
   - '--old.database.cutoffInMs=<Time of upgrade in Epoch format>'

   The value for the old.database.cutoffs parameter must be the day that you completed the upgrade with time as 12 midnight in Epoch time format.

   For example, if the date is 18th, June 2023, its Epoch timestamp in milliseconds is 1687046400000.
6. Click Save.

   The timeseries-0 Pod is restarted automatically.