Bug Description
org.apache.texera.web.service.ExecutionsMetadataPersistService.insertNewExecution (amber/src/main/scala/org/apache/texera/web/service/ExecutionsMetadataPersistService.scala:53) accepts uid: Option[Integer] and writes newExecution.setUid(uid.orNull), but workflow_executions.uid is declared NOT NULL in sql/texera_ddl.sql. Passing None therefore propagates a jOOQ DataAccessException("null value in column \"uid\" ... violates not-null constraint").
Either the column should be nullable or the method should refuse None (or take a required Integer). The signature/schema mismatch is silent today because every production caller passes Some(uid).
Reproduction
amber/src/test/scala/org/apache/texera/web/service/ExecutionsMetadataPersistServiceSpec.scala (introduced in the linked PR) pins this with intercept[org.jooq.exception.DataAccessException].
Version: 1.1.0-incubating.
Bug Description
org.apache.texera.web.service.ExecutionsMetadataPersistService.insertNewExecution(amber/src/main/scala/org/apache/texera/web/service/ExecutionsMetadataPersistService.scala:53) acceptsuid: Option[Integer]and writesnewExecution.setUid(uid.orNull), butworkflow_executions.uidis declaredNOT NULLinsql/texera_ddl.sql. PassingNonetherefore propagates a jOOQDataAccessException("null value in column \"uid\" ... violates not-null constraint").Either the column should be nullable or the method should refuse
None(or take a requiredInteger). The signature/schema mismatch is silent today because every production caller passesSome(uid).Reproduction
amber/src/test/scala/org/apache/texera/web/service/ExecutionsMetadataPersistServiceSpec.scala(introduced in the linked PR) pins this withintercept[org.jooq.exception.DataAccessException].Version: 1.1.0-incubating.