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
HPCC-21872 Old index values returned after index is overwritten #12520
HPCC-21872 Old index values returned after index is overwritten #12520
Conversation
@jakesmith Please review |
@richardkchapman there is a regression error (same on all engines) in this PR :
Somehow the Smoketest failed to put result report into GitHub. I'm investigating it. |
Hmm, by the log:"
It is strange, based on other test session (PR-12521) after this, finished and reported well. |
I pushed a fix |
I'm watching. |
Still strange. Smoketest wasn't able to add test session started comment to this PR. |
I wonder if it's because I blocked the SmokeTest user (I thought that would stop me getting notifications, but maybe it also stops smoketest from being able to comment on my PRs) |
I suspect that was it (having read the docs more carefully). I have unblocked - may also need to re-add as a collaborator. Let me know if you spot anything else I messed up. |
Yes, it seems. I tried to add a comment via browser as a Smoketest user and I wasn't able to do that. |
Test comment |
It seems ok now for Smoketest user.
Roxie:
|
Clear key cache for any index file that is written by hthor. For roxie, clear entire index key cache when a file is written (since the id's stored in the cache do not seem to correspond to physical filenames, it's non-trivial to clear just the one that is written. Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
I force-pushed another change. |
Automated Smoketest: ✅ Unit tests result:
Regression test result:
HPCC Stop: OK
|
I don't know where is the Smoketest report comment (by the logs it is created successfully), but this PR is clean now. |
@jakesmith Please review |
@@ -12290,6 +12290,7 @@ class CRoxieServerIndexWriteActivity : public CRoxieServerInternalSinkActivity, | |||
duplicateKeyCount = builder->getDuplicateCount(); | |||
cummulativeDuplicateKeyCount += duplicateKeyCount; | |||
builder->finish(metadata, &fileCrc); | |||
clearKeyStoreCache(false); |
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.
Curious why this isn't specifically clearing the file just written (as in the hthor change) ?
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.
I address this in the commit comment:
For roxie, clear entire index key cache when a file is written (since the id's
stored in the cache do not seem to correspond to physical filenames, it's
non-trivial to clear just the one that is written.
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.
ah ok, missed that.
@richardkchapman - one question |
@jakesmith See answer |
@richardkchapman - good to merge. |
@ghalliday Please merge |
Clear key cache for any index file that is written by hthor.
For roxie, clear entire index key cache when a file is written (since the id's
stored in the cache do not seem to correspond to physical filenames, it's
non-trivial to clear just the one that is written.
Signed-off-by: Richard Chapman rchapman@hpccsystems.com
Type of change:
Checklist:
Smoketest:
Testing:
using the test file in the Jira, which I added to the test suite.