-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: log malformed data during upsert ES docs #70
Conversation
Pull Request Test Coverage Report for Build 7407053139
💛 - Coveralls |
7221f01
to
6bab8f3
Compare
6bab8f3
to
5342b6e
Compare
@@ -61,6 +65,10 @@ func (m *InSituWorker) EnqueueSyncAssetJob(ctx context.Context, service string) | |||
|
|||
for _, ast := range assets { | |||
if err := m.discoveryRepo.Upsert(ctx, ast); err != nil { | |||
if strings.Contains(err.Error(), "illegal_argument_exception") { | |||
m.logger.Error(err.Error()) | |||
continue |
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.
@batrov just trying to understand here, if we have invalid format/argument for the field, we want to ignore it and keep processing remaining assets, but if we get any other error while upserting, we will return the error, without processing remaining assets?
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.
yes that is expected, that way the backed up index won't get deleted and we can analyze other error before retrying the sync job.
ignore_malformed
for object data type [ref]