francocalvo commented on issue #2267: URL: https://github.com/apache/fluss/issues/2267#issuecomment-3697580341
So... Done a a small test in a bigger server. 64GB RAM + 5800X processor. It's running Flink and Fluss. It's been 25min since the table started tiering to Paimon, but as you can see, no snapshots have been completed! <img width="801" height="391" alt="Image" src="https://github.com/user-attachments/assets/cc72cd29-28e1-417d-ac31-25194612af82"; /> <img width="721" height="156" alt="Image" src="https://github.com/user-attachments/assets/b281644f-2b72-4889-ae83-88aa6acff8db"; /> I can query the data in Flink using the Fluss Catalog and I'll give it to me, but if I try to change to batch mode, for example, it'll error out: ``` Flink SQL> SET 'execution.runtime-mode' = 'batch'; [INFO] Execute statement succeeded. Flink SQL> SELECT * FROM fluss_catalog.osb_staging.users_staging; [ERROR] Could not execute SQL statement. Reason: java.lang.UnsupportedOperationException: Currently, Batch mode can only be supported if one lake snapshot exists for the table. ``` What I'm not sure is what's making it so slow, how can I force it to create the snapshots, and if this is a hardware constraint or missconfiguration. The data is super small, no more than 100k entries for the biggest table. Maybe it's not hitting a threshold? I'll upload the repo tomorrow and link it here. I've followed some guides to get to this point, only difference I'm seeing is that I'm not using Paimon filesystem metastore, but using a JDBC one. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
