-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update to work with duckdb 1.1.1 #11
Conversation
🤯 This is awesome, thank you! I was just thinking the other day I wanted to do this. I'll try to take a look soon. :) |
You don't have to worry too much about the GH actions - those were mostly for building all the different artifacts and uploading to my own custom s3 bucket for hosting. With the new community extensions, looks like that's not relevant now. |
Thank you for considering my pull request! I know it's the holidays so no rush. Rust/C/C++ are not my strongest languages so happy to get any feedback and make any changes. Regarding the github actions, I don't mind trying to fix them (I don't think it's too much effort). If you don't think it is worth it or that it should be a different PR, that's fine too. |
I really appreciate the contribution. :) And holidays happen to be the perfect time hehe. Rust/C/C++ are not my strong suit either, but so far all the changes look good. I'm going to do some tests locally myself and if those pass, I say this PR can get merged and a subsequent one can be opened for the GH actions. |
@akumor Have you gotten this to build locally? I'm getting an error when running
There's a good chance my toolchains are not quite configured/versioned properly, so likely on my end, but wanted to double-check. |
yes, I was able to get it built locally before creating this PR 🤔 I am running Fedora linux so I did not test on a mac and I obviously did not get the github workflows running 🤔 |
kk, likely user error. :) Will do some more digging. |
Finally got it to build on mac - the change mentioned in the other comment helped, but I also had to revert some changes to the edit: it does build in Linux with the reverts from below.
|
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.
OK, I think with these changes it should build across linux/mac - haven't tested windows yet, but that's ok.
Once those change are made, I can merge in and then remove the existing GH actions as I'm pretty sure everything in those is taken care of by the new extension template.
In the (near) future, it'd be good to either just change this to a c++ extension or use the upcoming C extension API if rust is still desired.
…nfig.cmake work cross platform Co-authored-by: Damon P. Cortesi <[email protected]>
Co-authored-by: Damon P. Cortesi <[email protected]>
Co-authored-by: Damon P. Cortesi <[email protected]>
dcdf776
to
56ab2ce
Compare
I think I have addressed all of the comments on the PR now. Let me know if you would like to see any other changes.
I agree! My personal bias would be to keep rust because of my own personal interests and because I think it might make it easier to contribute. Regardless of direction, I would be willing to take a stab at this unless you feel particularly inclined to take it on. I am particularly interested in adding support for different databases as described in this issue too. |
Feel free! You'll definitely get to it before I will - I don't know much about the upcoming extension API. Will get this merged in. |
This PR contains changes I made to get the duckdb-athena-extension to work with version 1.1.1 of duckdb. It includes changes to make use of extension-ci-tools and libduckdb_sys from duckdb-rs .