Currently it is necessary for a Spidered table to be created separately on each node in the Spider cluster. This process by the end user is time-consuming, repetitive and error-prone.

      To simplify this, we can have the Spider node push down the CREATE TABLE statement to each of the data nodes. The statement pushed down to the data nodes would not have the COMMENT that is used to specify the connection information.

      In case of a failure on any of the data nodes, Spider would potentially need to do cleanup to synchronize the table definition across the Spider cluster. Since DDLs are not transactional, the table cleanup would need to be implemented in the Spider node without the benefit of a rollback to remove the table definition throughout the cluster.

      We would also add a new Spider configuration setting to specify :

      Whether CREATE OR REPLACE TABLE is appropriate on the data nodes.


          Issue Links



              • Assignee:
                Kentoku Kentoku Shiba
                jacob-mathew Jacob Mathew (Inactive)
              • Votes:
                0 Vote for this issue
                6 Start watching this issue


                • Created: