Closed shmuelf closed 2 years ago
I originally created this project with the intent to have a branch for each version of presto that needed updated support so there wasn't a complicated selection of classes to serde against for changes in the original java code (with main duplicating the latest version). I still think that's the approach I'm going to stick with (but open to hear options). Which version did you test this against?
Also, I haven't been solely targeting the latest .net version to maintain compatibility for older runtimes. For example, there was a time when AWS Lambda functions could only use netstandard1.6. But happy to add .net5 as well.
I originally created this project with the intent to have a branch for each version of presto that needed updated support so there wasn't a complicated selection of classes to serde against for changes in the original java code (with main duplicating the latest version). I still think that's the approach I'm going to stick with (but open to hear options). Which version did you test this against?
Also, I haven't been solely targeting the latest .net version to maintain compatibility for older runtimes. For example, there was a time when AWS Lambda functions could only use netstandard1.6. But happy to add .net5 as well.
Thank you for your reply @hakenmt , the server version I ran against was 0.256
I've taken these changes and merged them into a new branch 0.256. Thanks for the submission.