-
Notifications
You must be signed in to change notification settings - Fork 210
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
[Online Scoring] Automation Rules endpoints #945
base: main
Are you sure you want to change the base?
Conversation
Data model, DAO, service layer and endpoints for Automation Rule Evaluators. I've started with a more complicated approach, but in the end decided for a much simpler one which hopefully is easy enough to extend later into non-evaluator automation rules. Also as we've decided for a non-validation approach in the code, we're just going with a text field. ## Issues OPIK-590 OPIK-591
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.
As discussed in the design, the rule, action and evaluator can be up to 3 different entities. Fine to go with an approach where they're all collapsed into 1 in order to deliver faster. However, this can make extendability for future requirements harder.
For this PR, focus on making the evaluator payload a polymorphic value, so we can define any type of evaluator (python, llm as a judge). The current code
field of type string
is a concerning implementation.
Then review a bit the paths of the new resource and adjust them.
Everything else is minor polishings. I didn't go in the tests deeply, as still commented out and because this is in-progress.
Thank you very much for putting this together and congrats for your first PR in Opik!
apps/opik-backend/src/main/java/com/comet/opik/api/AutomationRuleEvaluator.java
Outdated
Show resolved
Hide resolved
apps/opik-backend/src/main/java/com/comet/opik/api/AutomationRuleEvaluator.java
Outdated
Show resolved
Hide resolved
@JsonView({View.Public.class, | ||
View.Write.class}) @Pattern(regexp = NULL_OR_NOT_BLANK, message = "must not be blank") String code, |
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.
This field should probably be a polymorphic model, so we can define LLM as a judge evaluators and python evaluators, with different payloads.
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.
Let's update code to be a JsonNode.
return new AutomationRuleEvaluator.AutomationRuleEvaluatorPage(page, 0, 0, List.of()); | ||
} | ||
} | ||
} |
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.
Minor: run spotless on your PRs, so code is automatically formatted.
This is a previous miss from our side, we need to automate this.
...end/src/main/java/com/comet/opik/api/resources/v1/priv/AutomationRuleEvaluatorsResource.java
Outdated
Show resolved
Hide resolved
apps/opik-backend/src/main/java/com/comet/opik/domain/AutomationRuleDAO.java
Outdated
Show resolved
Hide resolved
apps/opik-backend/src/main/java/com/comet/opik/domain/AutomationRuleService.java
Outdated
Show resolved
Hide resolved
} | ||
|
||
@Override | ||
public Optional<AutomationRuleEvaluator> getById(@NonNull UUID id, @NonNull UUID projectId, |
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.
Redundant.
} | ||
|
||
@Override | ||
public AutomationRuleEvaluator findById(@NonNull UUID id, @NonNull UUID projectId, @NonNull String workspaceId) { |
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.
Just overload the method by wrapping the id in a set.
...d/src/main/resources/liquibase/db-app-state/migrations/000008_add_automation_rule_tables.sql
Outdated
Show resolved
Hide resolved
…o be based in a sample
…rogramming in case the string changes.
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.
This is in better state, but let's keep polishing.
import java.util.Arrays; | ||
import java.util.UUID; | ||
|
||
public sealed interface AutomationRule<T> permits AutomationRuleEvaluator { |
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.
Let's make this interface and its subclasses self de/serialisable without requiring any external help. You just need to configure it with JsonTypeInfo
and JsonSubTypes
annotations etc., based on the action
property.
@JsonIgnoreProperties(ignoreUnknown = true) | ||
@JsonNaming(PropertyNamingStrategies.SnakeCaseStrategy.class) | ||
public record AutomationRuleEvaluatorUpdate( | ||
@NotBlank String code, |
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.
Same, let's change code
to a JsonNode field.
...end/src/main/java/com/comet/opik/api/resources/v1/priv/AutomationRuleEvaluatorsResource.java
Show resolved
Hide resolved
...end/src/main/java/com/comet/opik/api/resources/v1/priv/AutomationRuleEvaluatorsResource.java
Show resolved
Hide resolved
...end/src/main/java/com/comet/opik/api/resources/v1/priv/AutomationRuleEvaluatorsResource.java
Show resolved
Hide resolved
CREATE TABLE IF NOT EXISTS automation_rule_evaluators ( | ||
id CHAR(36), | ||
|
||
`type` ENUM('llm_as_judge', 'python') NOT NULL, |
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.
Same.
...d/src/main/resources/liquibase/db-app-state/migrations/000009_add_automation_rule_tables.sql
Show resolved
Hide resolved
...d/src/main/resources/liquibase/db-app-state/migrations/000009_add_automation_rule_tables.sql
Show resolved
Hide resolved
INDEX `automation_rules_idx` (workspace_id, project_id, id) | ||
); | ||
|
||
CREATE TABLE IF NOT EXISTS automation_rule_evaluators ( |
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.
As general convention, we denormalise created_at
etc. fields in all tables.
@JsonView({View.Public.class, | ||
View.Write.class}) @Pattern(regexp = NULL_OR_NOT_BLANK, message = "must not be blank") String code, |
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.
Let's update code to be a JsonNode.
Details
Data model, DAO, service layer and endpoints for Automation Rule Evaluators.
I've started with a more complicated approach, but in the end decided for a much simpler one which hopefully is easy enough to extend later into non-evaluator automation rules. Also as we've decided for a non-validation approach in the code, we're just going with a text field.
Issues
OPIK-590
OPIK-591
Testing
Documentation