Indexed view using DATA_STRUCTURE and fetch

[kavilla]

Description

Very rough implementation of indexed view using the DATA_STRUCTURE generic object can handle this concept of indexed view.

I didn't do any clean up and it has mocked data of S3 . So i can summarize the basic changes.
Here I'm defining DATASET object. If the data type can supported Indexed Views, it will call a fetch with that current dataset. It can then know it is time to fetch my indexed views. If the user selects an index view then it will update the dataset with the indexed view but store a ref to the original data.

This way we are leveraging existing features since we should have everything we need at the point of time of selection.

Benefits

• Follows the existing pattern with supports vs checking if a service is defined on the config
• Re-uses existing functionality already covered by unit tests reducing how big the config is getting
• Re-purposes a function that is generic enough to handle it while also using a generic data structure which leaves open the door for other data types to re-use this functionality

Issues Resolved

#8851

Screenshot

• Able to query S3 table directly
  
• Selecting an that same table but with an indexed view (using an existing index)
  
• Queries the selected indexed view
  

Testing the changes

Changelog

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[github-actions]

❌ Empty Changelog Section

The Changelog section in your PR description is empty. Please add a valid changelog entry or entries. If you did add a changelog entry, check to make sure that it was not accidentally included inside the comment block in the Changelog section.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.39%. Comparing base (76cf823) to head (80d028b).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8845      +/-   ##
==========================================
- Coverage   60.86%   56.39%   -4.48%     
==========================================
  Files        3800     1239    -2561     
  Lines       90818    25913   -64905     
  Branches    14307     4437    -9870     
==========================================
- Hits        55276    14613   -40663     
+ Misses      32028    10559   -21469     
+ Partials     3514      741    -2773     

Flag	Coverage Δ
Linux_1	?
Linux_2	56.39% <ø> (ø)
Linux_3	?
Linux_4	?
Windows_1	?
Windows_2	?
Windows_3	?
Windows_4	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

❌ Empty Changelog Section

The Changelog section in your PR description is empty. Please add a valid changelog entry or entries. If you did add a changelog entry, check to make sure that it was not accidentally included inside the comment block in the Changelog section.

[github-actions]

❌ Empty Changelog Section

The Changelog section in your PR description is empty. Please add a valid changelog entry or entries. If you did add a changelog entry, check to make sure that it was not accidentally included inside the comment block in the Changelog section.