Skip to content

Conversation

@abhijeet-atlan
Copy link

@abhijeet-atlan abhijeet-atlan commented Jan 27, 2025

DG1924
Design plan ref :Execution Plan - Phase v1 - WIP | 1. Task Vertex
Test cases: DG1924 - TestCase

The task for this ticket:

Add 'assetsCountToPropagate' and 'assetsCountPropagated' params to the task vertex and

update 'assetsCountToPropagate' with a count of the assets count to propagate once the planning phase is finished.
update 'assetsCountPropagated' with a count as the task progresses.

Type of change

  • Bug fix (fixes an issue)
  • New feature (adds functionality)

Related issues

Fix #1

Checklists

Development

  • Lint rules pass locally
  • Application changes have been tested thoroughly
  • Automated tests covering modified code pass

Security

  • Security impact of change has been considered
  • Code follows company security practices and guidelines

Code review

  • Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached as necessary
  • "Ready for review" label attached and reviewers assigned
  • Changes have been reviewed by at least one other contributor
  • Pull request linked to task tracker where applicable

jnkrmg
jnkrmg previously approved these changes Jan 28, 2025
Copy link

@jnkrmg jnkrmg left a comment

Choose a reason for hiding this comment

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

LGTM!

//update the 'assetsCountToPropagate' in the current task vertex.
AtlasVertex currentTaskVertex = (AtlasVertex) graph.query().has(TASK_GUID, currentTask.getGuid()).vertices().iterator().next();
currentTaskVertex.setProperty(TASK_ASSET_COUNT_TO_PROPAGATE, currentTask.getAssetsCountToPropagate());
graph.commit();

Choose a reason for hiding this comment

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

remove graph.commit()

Copy link
Author

Choose a reason for hiding this comment

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

Wrote a new function updateTaskVertexProperty that is used everywhere and it doesn't have graph.commit() in it.

List<AtlasGraphQuery> orConditions = new LinkedList<>();
orConditions.add(query.createChildQuery().has(Constants.TASK_STATUS, AtlasTask.Status.IN_PROGRESS));
orConditions.add(query.createChildQuery().has(Constants.TASK_STATUS, AtlasTask.Status.PENDING));
orConditions.add(query.createChildQuery().has(TASK_STATUS, AtlasTask.Status.IN_PROGRESS));

Choose a reason for hiding this comment

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

reason for these changes?

Copy link
Author

Choose a reason for hiding this comment

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

I have reverted these back

Copy link

@sumandas0 sumandas0 left a comment

Choose a reason for hiding this comment

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

Mostly reviews are for code quality

@abhijeet-atlan abhijeet-atlan requested review from sumandas0 and removed request for Madusudanan February 3, 2025 03:45
@abhijeet-atlan
Copy link
Author

removed madu from review because of new team structure

jnkrmg and others added 3 commits February 4, 2025 11:58
…k vertex. The former will be updated with the total count of propagations to be done once the planning phase is complete and the task begins execution. The latter will be updated as the task progresses, reflecting the count of completed propagations at any given point.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants