Skip to content
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

Task/improve performance persist aggregation mongo sink #2031

Merged

Conversation

AlvaroVega
Copy link
Member

@AlvaroVega AlvaroVega commented May 13, 2021

fix for #2019

@AlvaroVega AlvaroVega requested a review from fgalan May 13, 2021 13:20
@AlvaroVega AlvaroVega changed the title [WIP] Task/improve performance persist aggretation mongo sink Task/improve performance persist aggretation mongo sink May 13, 2021
@AlvaroVega AlvaroVega changed the title Task/improve performance persist aggretation mongo sink Task/improve performance persist aggregation mongo sink May 13, 2021
Copy link
Member

@fgalan fgalan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fgalan fgalan merged commit f1f7d49 into master May 14, 2021
@fgalan fgalan deleted the task/improve_performance_persist_aggretation_mongo_sink_ branch May 14, 2021 06:56
throw new CygnusPersistenceError("-, " + e.getMessage());
} catch (Exception e1) {
try {
// try insert without create collection before
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// try insert without create collection before
// try to insert without create database before, but creating the collection

I was reviewing this PR for the TSC preparation. This comment seems wrong from my point of view. It is not "try to insert without create database before, but creating the collection?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The suggested wording makes sense from my point of view. Could you make a PR fixing the comment, pls?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants