-
Notifications
You must be signed in to change notification settings - Fork 141
feat(catalog/sql): Add views related ops #414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Hey @dttung2905, just wanted to check if you're still actively working on this PR. If not, I'd be happy to pick it up and continue. Let me know your thoughts! |
Hello 👋, yes, i was still working on it. Its taking longer than usual sorry. Will update the code some time today for review |
80ce8a4 to
2b6e025
Compare
zeroshade
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a few comments but overall looks good to me so far.
Is there any way we can set up an integration test to compare against other implementations?
@zeroshade Thanks for the review. I have made some changes for the linting which should make the CI passes. Regarding the integration test, I think its a good idea. I'm working on something similar to |
|
A follow up PR for the integration test is fine. If you're not gonna start immediately after this gets merged, then let's file an issue to track it so we don't forget. But if you'll be following up quickly with the test, no need for an issue. 😄 |
|
@zeroshade It seems like the go-integration test is failing which other PR also encounters. I don't think it is related to any changes related to this PR. Do you have any idea how to fix it? I will try to rebase from main to see if the CI passes |
62aa3b3 to
43a8540
Compare
|
@dttung2905 this is super weird. I can't replicate the failure locally. It looks like it's getting some kind of error trying to write to the minio instance. @Fokko @kevinjqliu any ideas what could be going wrong here? Looks like it's failing inside of pyiceberg's |
|
@dttung2905 figured out the issue, #444 fixes it so you can rebase once that gets merged. |
Sure. Let me rebase it again in a few hours. Thanks alot for the quick fix |
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
43a8540 to
935cad1
Compare
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
zeroshade
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks!
No description provided.