-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Implement elastic search issue indexer interface #6150
Conversation
bef5278
to
316de4c
Compare
It's ready for review now. |
Codecov Report
@@ Coverage Diff @@
## master #6150 +/- ##
=========================================
Coverage ? 40.14%
=========================================
Files ? 404
Lines ? 54263
Branches ? 0
=========================================
Hits ? 21786
Misses ? 29461
Partials ? 3016
Continue to review full report at Codecov.
|
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.
Hi lunny!
Looks good overall however I think you need to do a general search and replace of Done!elestic
for elastic
.
Your choice of a skip of 2 for the elastic logger seems unusual. 1 is usually correct as it points to where the Printf is called, unless elastic wraps the Printf itself in which case 2 is appropriate. I've just doublechecked the source. You're right!
You still need to add config stubs to modules/setting/log.go
. Basically you need a setting ELASTIC
which configures which sublogging modes that would use. You could make this generic and name it INDEXER
? Then you could use the same named logger for different types of indexer?
316de4c
to
44637ed
Compare
|
||
if !exists { | ||
mapping := `{ | ||
"settings":{ |
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.
Would be nice if this could be moved out to embedded file so that it could be customized using custom directory
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.
Maybe a config item on app.ini to point to a mapping file which default are empty is better?
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.
that could also be an option
44637ed
to
8f20faf
Compare
49ac4b8
to
1bf75b6
Compare
1bf75b6
to
ab901c9
Compare
@lunny do you know how long this will take to be implemented? |
These PRs should my next work since migration PR merged. But I can't give you some date. |
Thanks so it will definitly be in the next version 1.9.x? |
ab901c9
to
ceec710
Compare
ceec710
to
d9699ef
Compare
63e9a4f
to
cdce7f9
Compare
conflicts |
cdce7f9
to
e81618c
Compare
…t for elastic search
e81618c
to
6886071
Compare
8559553
to
40b7f55
Compare
@lunny I got this: https://zuul.opendev.org/t/openstack/build/ddba351742a84e66947928231e6a02ff/log/gitea99.opendev.org/docker/giteadocker_gitea-web_1.txt#5319 which maybe looks like the code is trying to create the elasticsearch index twice? there's still something else wrong with that patch, so I'm not 100% sure yet |
@lunny nevermind. that's a log line about repo indexer. I think I found another issue in my test job - I'll let you know how the latest version goes |
Replaced by #9428 |
No description provided.