Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Who agreed with this solution

avatar
Contributor
Hi,
The issuing a REFRESH will broadcast the updated table to all nodes. There
may be a short delay after the command completes before the changes are
visible on remote nodes. This is because we must wait for a statestore
update to propagate the changes out.

If you need stronger consistency guarantees (the change is visible on all
nodes at the time it completes) you can use the query option:
SET SYNC_DDL=true

This will impact DDL performance, so it is disabled by default. For optimal
performance, you can batch your DDL statements and only enable this query
option for the final statement in the batch. For example:

> connect to node 1
CREATE TABLE Foo
ALTER TABLE ADD PARTITION 1
..
SET SYNC_DDL=true
ALTER TABLE ADD PARTITION N

> connect to node2
SELECT * FROM TABLE

Thanks,
Lenni

View solution in original post

Who agreed with this solution