You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Brian Hulette (Jira)" <ji...@apache.org> on 2019/11/19 16:51:00 UTC

[jira] [Created] (BEAM-8741) Queries that attempt to write to pubsub publish time should fail

Brian Hulette created BEAM-8741:
-----------------------------------

             Summary: Queries that attempt to write to pubsub publish time should fail
                 Key: BEAM-8741
                 URL: https://issues.apache.org/jira/browse/BEAM-8741
             Project: Beam
          Issue Type: Improvement
          Components: dsl-sql
            Reporter: Brian Hulette


Currently it's possible to perform a query like:

{code:sql}
CREATE TABLE pubsub (
  event_timestamp TIMESTAMP,
  id VARCHAR
) ...

INSERT INTO pubsub (event_timestamp, id) VALUES (...)
{code}

But when this is executed, the event_timestamp will be dropped, because on read it will be instead be populated with pubsub's publish time.

We should somehow indicate that this is a VIRTUAL GENERATED column, and is therefore read-only. Calcite seems to have some support for this concept, see [ColumnStrategy.java|https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/schema/ColumnStrategy.java].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)