GitHub user kz930 added a comment to the discussion: Scaling verification of
workflow to Python translation — looking for input
Agreed — fully automating property-filling across domains isn't reliable, so
we don't aim
for that. In practice it splits in two: **type** covers most column fields
automatically
(from the operator's existing `attributeTypeRules`), and only
**value-domain** fields
(e.g. a p-value in (0,1), a country code) need a **one-line annotation** on
the field —
essentially your "operator declares how to fill itself," reduced to one line
rather than a
full config method. So most operators need no per-operator code.
On the per-operator sample dataset: we currently lean toward one shared table
with
typed/domain columns, so an operator just points at a column instead of
shipping its own
data. But your `sampleData()`-per-operator is a clean fallback for inputs the
shared table
can't express (image / model / training-style) — I'll use it there.
GitHub link:
https://github.com/apache/texera/discussions/6072#discussioncomment-17520072
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
