Skip to content

Conversation

@manojdbos
Copy link
Contributor

Most basic:

Sync invocation of workflow
updates to workflow_status

@manojdbos manojdbos marked this pull request as ready for review June 18, 2025 22:54
README.md Outdated
https://adoptium.net/en-GB/temurin/releases/?os=any&arch=any&version=21

Recommended IDE IntelliJ (Community edition is fine).
But feel free to use vi, if you are more comfortable with it.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Or VS Code! :)

Copy link
Member

Choose a reason for hiding this comment

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

nit: this file path name should be migrations instead of migration because we're going to have a lot more migrations in the future.


CREATE INDEX workflow_status_created_at_index ON dbos.workflow_status USING btree (created_at);
CREATE INDEX workflow_status_executor_id_index ON dbos.workflow_status USING btree (executor_id);
CREATE INDEX workflow_status_status_index ON dbos.workflow_status USING btree (status);
Copy link
Member

Choose a reason for hiding this comment

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

Let's remove the tables that aren't used from this file (workflow inputs and workflow events)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

workflow_events will be needed when we do events right ? Or No ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

removed workflow_inputs

}
}

public static class UpdateWorkflowOptions {
Copy link
Member

Choose a reason for hiding this comment

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

I don't understand what this big class is?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is the same UpdateWorkFlowOPtions from TS and python for the updateWorkflowStatus method. The update sql is generated based on options provided.

Large ness is due to Java verbosity with get/set methods

Logger logger = LoggerFactory.getLogger(SimpleServiceImpl.class);

@Workflow(name = "workWithString")
public String workWithString(String input) {
Copy link
Member

Choose a reason for hiding this comment

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

To make sure I'm clear: later on, we'll make it so workflows always return handles?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have thought about how it will be done. We can talk about it

@manojdbos manojdbos merged commit 6ecbd7d into main Jun 20, 2025
1 check passed
@chuck-dbos chuck-dbos deleted the manoj/sync_invocation branch August 25, 2025 20:38
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.

5 participants