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

fix(gms): filter out runs of a dataJob without any run-events #11223

Merged

Conversation

ksrinath
Copy link
Contributor

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Copy link
Contributor

coderabbitai bot commented Aug 22, 2024

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added product PR or Issue related to the DataHub UI/UX community-contribution PR or Issue raised by member(s) of DataHub Community labels Aug 22, 2024
@ksrinath ksrinath reopened this Aug 28, 2024
Copy link
Collaborator

@david-leifker david-leifker left a comment

Choose a reason for hiding this comment

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

None of this code is required to add a hasXXX field and this implementation is not correctly handling the ES index mapping.

This feature should be implemented by adding a @searchable annotation to the entity on the timeseries field in the pdl model. This is done with an annotation called hasValuesFieldName and will both update the ES mapping and populate the boolean without any additional code beyond the addition to the annotation.

@@ -15,6 +15,10 @@ import com.linkedin.common.Urn
record DataProcessInstanceRunEvent includes TimeseriesAspectBase, ExternalReference {

@TimeseriesField = {}
@Searchable = {
"fieldType": "TEXT",
Copy link
Collaborator

Choose a reason for hiding this comment

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

This should either be removed or set to KEYWORD. The reason is that the value is of type enum which would default to KEYWORD.

Copy link
Collaborator

@david-leifker david-leifker left a comment

Choose a reason for hiding this comment

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

The upgrade job looks really good!

  1. Add a delayMs to the primary while loop. This should be set to a default of 1000 millis. The reason is that we want to throttle a little as the aggregation query can put load on the ES cluster and allows us to increase the delay if it triggers alerts on the cluster.
  2. The aggregation query should specify a time window start/stop on the timeseries aspect index. We've seen negative performance impacts from querying the entire timeseries indices (A customer with large timeseries would be Robinhood for example). I would expect the query to iterate on buckets of time. For example, a 1 day window. - Bonus points if the window is fully configurable, but a good conservative default would be to aggregate timeseries data 1 day at a time and maybe assume that it processes the last 90d.

Copy link
Collaborator

@david-leifker david-leifker left a comment

Choose a reason for hiding this comment

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

The aggregation query will only return batchSize (top N) urns from the timeseries index. How does this code not just update the batchSize most frequent entities?

@ksrinath
Copy link
Contributor Author

ksrinath commented Sep 4, 2024

The aggregation query will only return batchSize (top N) urns from the timeseries index. How does this code not just update the batchSize most frequent entities?

The afterKey is updated in the outer-indefinite-while loop, so that all the distinct-urns should get read by the time we break out of the while-loop. Am I missing something here?

@ksrinath
Copy link
Contributor Author

ksrinath commented Sep 5, 2024

  1. Add a delayMs to the primary while loop. This should be set to a default of 1000 millis. The reason is that we want to throttle a little as the aggregation query can put load on the ES cluster and allows us to increase the delay if it triggers alerts on the cluster.

Updated code for this; can you please review.

@david-leifker david-leifker self-assigned this Sep 6, 2024
@david-leifker
Copy link
Collaborator

The aggregation query will only return batchSize (top N) urns from the timeseries index. How does this code not just update the batchSize most frequent entities?

The afterKey is updated in the outer-indefinite-while loop, so that all the distinct-urns should get read by the time we break out of the while-loop. Am I missing something here?

RIght, it is using the Composite aggregator here. It should work.

@david-leifker
Copy link
Collaborator

@ksrinath - I am not seeing delayMs - missing changes?

@ksrinath
Copy link
Contributor Author

  1. The aggregation query should specify a time window start/stop on the timeseries aspect index. We've seen negative performance impacts from querying the entire timeseries indices (A customer with large timeseries would be Robinhood for example). I would expect the query to iterate on buckets of time. For example, a 1 day window. - Bonus points if the window is fully configurable, but a good conservative default would be to aggregate timeseries data 1 day at a time and maybe assume that it processes the last 90d.

Can you please review the updated code.

Copy link
Collaborator

@david-leifker david-leifker left a comment

Choose a reason for hiding this comment

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

LGTM! Great job!

@ksrinath ksrinath marked this pull request as ready for review September 11, 2024 04:36
@david-leifker david-leifker merged commit fd6d4c8 into datahub-project:master Sep 11, 2024
73 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-contribution PR or Issue raised by member(s) of DataHub Community product PR or Issue related to the DataHub UI/UX
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants