Right now the declared schema in the studio doesn't influence the things that will happen in the runtime for tck connectors.
As a user, I can define not nullable column but in the runtime the scheme but in the runtime those files are going to be nullable anyway.
Like on the screenshots from the https://jira.talendforge.org/browse/TUP-33208
We can reproduce the behavior with the attach in remote debug to this job.
It uses Neo4j connector
Like on the screen:
Expected that in the result when the user defines not nullable columns those columns will be not nullable in the runtime too.
We can generate some static information inside a row structure.