santiagoguinle commented on issue #11418: URL: https://github.com/apache/druid/issues/11418#issuecomment-877252588
Well, at least for now i am following your recommendation. i already made the test: i downloaded the code, changed it (just deleted the "FOR UPDATE" string), recompiled, configured to work with SQLServer and works perfect. Aparently is the only line of code that brings incompatibility. i even tryied some ingestion tasks and everything went great. Of course, probably it would be necesary to make a bigger change in order to maintain the functionality of locking rows. I also notice that Druid indeed has several files in his core dedicated to deal with SQLServer. But this "bug" was writed in a core class file, so an extension doesn't look like the place to fix it. So, i am pretty sure that #7661 was a great improvement and fix some problems but also creates a incompatibility with a great DB Engine. I dont do JAVA programming, so meaby im not the correct person for helping with this... BUT i will be happy to help in order to keep improving Druid, so let me know if i can do something. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
