Skip to content

A small flaw regarding the deployments table. #1264

Closed
@frg01

Description

@frg01

A default mechanism for train deployment is best_score, but why is the strategy field in the deployments table a fixed value most_recent? If it is to record the strategy during deployment, then it is best to be a variable. If it is to query during deployment, then it It seems like another redundant field. Maybe I don’t understand this table well enough. If possible, I’d like to ask you for advice!

`select pgml.train(
project_name => 'Diabetes Regression',
task => 'regression',
relation_name => 'pgml.diabetes',
y_column_name => 'target',
algorithm=> 'linear'
);

select * from pgml.deployments
results :
id | project_id | model_id | strategy | created_at
----+------------+----------+-------------+----------------------------
3 | 2 | 4 | most_recent | 2024-01-03 10:52:12.474621
5 | 2 | 7 | most_recent | 2024-01-03 10:55:03.908885
4 | 2 | 5 | most_recent | 2024-01-03 10:54:20.831898
2 | 2 | 2 | most_recent | 2024-01-03 10:47:02.574409
1 | 1 | 1 | most_recent | 2024-01-03 10:29:18.626135

`

Thank you for your continuous explanations these days. If I find new problems, I may need to trouble you. Thank you more.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions