-
Notifications
You must be signed in to change notification settings - Fork 11
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
[#128] Update for iRODS 4.3.1 (main) #131
Conversation
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.
Any guidance on how to review this would be helpful, given its size and the fact that not all of it is new. I've mainly been responding to your comments that solicit responses :) Thanks
commit e42cc22 has typo in commit message (elasticlist) |
The bulk of the line changes are formatting. So clicking through the commits one by one made it easier to see what was going on / ignore the clang formatting. |
Right. Definitely better to view each commit separately. Once I resolve the current comments, I'll squash and it should be easier to read. I'll put this in draft for now. |
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.
Hopefully some of these aren't out of date...
NTS: Test TLS support. |
Noting here that TLS with ES requires authentication. I don't think this plugin currently supports configuration options for that. Also, the ESv8 docker container generates the necessary certs for you to test it. You can read about it here. I think TLS support will need to happen in a separate PR or later release. |
That's okay - we can get it working/compiling/happy with the latest other things, and get TLS added quick as soon as someone needs it. |
Apparently we do have an issue for TLS. See #112 |
After some discussion, we've decided to remove the document_type REP. The reason behind this change is because elasticsearch no longer supports mapping types. For more information, see https://www.elastic.co/guide/en/elasticsearch/reference/7.17/removal-of-types.html. |
Cleaned up commits. Running tests. |
All tests pass (minus the atomic avu one). Tested using the testing environment (ES v7.4). |
Ran the tests again to make sure things work after that last commit. I need to revisit the postinst script commit though. |
Everything seems good to me so far. Will await word on the postinst script. |
Perhaps removing those references to the postinst script is better since the cmake file defines the following. irods_capability_indexing/CMakeLists.txt Lines 104 to 112 in 82eee54
Will run the tests for CentOS 7 and the Almalinux / Rocky Linux to verify. |
I've confirmed the changes pass the tests for CentOS 7. I cannot run the tests for Almalinux 8 and Rocky Linux 9 due to docker and python pip issues. Regardless, I was able to confirm the packages produced by this PR install without issues for these platforms. All I have to do now is assign issues and we're good to go. |
Issue numbers assigned. Just need that good ole approval. |
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.
Seems good to me. Let's do it
Added #'s |
Aside from a few recent changes, I've seen this code pass the test suite against Elasticsearch 7.4.2 and 8.12.1.
Below are the test results for Elasticsearch 8.12.1. Notice the atomic metadata ops test was skipped. I think this is mostly fine given the fact that the atomic APIs are relatively stable. I'll see if I can track down how to properly handle that test case.
Now we need to think through how to incorporate testing of Elasticsearch 8. To test it, I launched an Elasticsearch container and ran the tests at the bench. We'll need to decide whether it's worth modifying the test hook or moving towards a docker compose like setup.
Forgot to mention - this PR also formats all of the C++ code. It's better to view the commits individually so you see what the true changes for 4.3.1 are.