Fix: Correct the profile of cache layer schema for Canner Persistence Store #276
+28
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
For the Canner Enterprise product, the extension-store-canner pulls the result.json from Minio to merge into one file, it lacks the profile setting of the cache layer in the schema, so we need to fix it and let caching datasets functionality works.
Issue ticket number
closes #275
Screenshot for integrating with Canner Enterprise.
Step 1: Check the connection and deploy Data API to the Canner Enterprise product
Step 1-1
Opened a Canner Enterprise of PR testing env and create the

w1
workspaces with the table:Step 1-2.1
Use the In the VulcanSQL labs and create canner-w1 profiles with temporal PAT for connecting Canner Enterprise by extension-driver-canner through PG Wire Protocol:

Step 1-2.2
Enable caching for vulcan.yaml
Step 1-2.3
Apply my bugfix code for
package.json
of labsStep 1-3
Prepare Data APIs

Step 1-4
Add pkg-extension-store-canner in the Makefile and execute it
(Get the result.json)
Step 1-5
Upload them to Canner Enterprise, and see the uploaded artifacts in the vulcansql folder of w1:

Step 2: Check CannerPersistenceStore
Now we delete the SQLs and API schemas files, in the lasbs project, and update the vulcan.yaml for artifact options, extensions and profiles like below to use the Canner extension:
Step 2-1
Step 2-2
Then set some environment variables we need:
Step 2-3.1
Finally, run vulcan serve to fetch the artifacts from Canner Enterprise, and generate Canner Enterprise Profiles settings:

Step 2-3.2
Open the API documentation URL, we will see the workspace SQL Name in the prefix for the w1 Data API:

Step 2-3.3
Send request to

/api/w1/activity_logs?operation=LOGIN
to query and you will see the result:Done.
Additional Context
I will revert #273 in this PR as it was causing bugs with the Canner integration. It seems that this issue needs to be discussed in an Issue. cc @cyyeh