fix: Add vector database doc by HaoXuAI · Pull Request #4165 · feast-dev/feast
What this PR does / why we need it:
Add the instruction document for vector database
Which issue(s) this PR fixes:
Fixes
Signed-off-by: cmuhao <sduxuhao@gmail.com>
| Then run the following command to materialize the data to the online store: | ||
|
|
||
| ```shell | ||
| !feast materialize 2024-04-01T00:00:00 2024-04-17T00:00:00 |
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would suggest the below so time doesn't impact this
| !feast materialize 2024-04-01T00:00:00 2024-04-17T00:00:00 | |
| ```shell | |
| CURRENT_TIME=$(date -u +"%Y-%m-%dT%H:%M:%S") | |
| feast materialize-incremental $CURRENT_TIME |
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Overall lgtm. I'll try to clean up the full demo this week.
CC @jeremyary can we include this in 37.1?
| feast apply | ||
| ``` | ||
|
|
||
| Then run the following command to materialize the data to the online store: |
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Then run the following command to materialize the data to the online store: | |
| Then run the following command in the terminal to materialize the data to the online store: |
Nice! Overall lgtm. I'll try to clean up the full demo this week.
CC @jeremyary can we include this in 37.1?
hmm, with it being just a doc, I think it may sync to gitbook with just a cherry-pick to v0.37-branch and maybe a nudge on gitbook side. That said, we've got a lot of goodies going in this week so I was considering a 0.38 cut before too awful long
Signed-off-by: Hao Xu <sduxuhao@gmail.com>
Run aws-actions/amazon-ecr-login@v1
Warning: Your docker password is not masked. See https://github.com/aws-actions/amazon-ecr-login#docker-credentials for more information.
Error: User: arn:aws:iam::***:user/feast is not authorized to perform: ecr:GetAuthorizationToken on resource: * because no identity-based policy allows the ecr:GetAuthorizationToken action
@jeremyary looks like there is a aws auth issue.
Signed-off-by: cmuhao <sduxuhao@gmail.com>
