Using the mixed-hive table format, non-hive server2 writes at first, and the write&query is normal. After turning on the base.hive.auto-sync-data-write=true parameter, use hiveserver2 to write to the table, and use amoro query again, the data can only be queried. Written to hiveserver2. Then after writing to base, both hive and base can be found.
hiveserver2 insert into the table
In fact, I wrote a large amount of base table data，But only hiveserver2 insert can be queried here.
When base.hive.auto-sync-data-write=true , the table record becomes consistent with the number of data inserted by hiveserver2.
Affects Versions
0.6.0
What engines are you seeing the problem on?
No response
How to reproduce
No response
Relevant log output
No response
Anything else
No response
Are you willing to submit a PR?
[ ] Yes I am willing to submit a PR!
Code of Conduct
[X] I agree to follow this project's Code of Conduct
What happened?
Using the mixed-hive table format, non-hive server2 writes at first, and the write&query is normal. After turning on the base.hive.auto-sync-data-write=true parameter, use hiveserver2 to write to the table, and use amoro query again, the data can only be queried. Written to hiveserver2. Then after writing to base, both hive and base can be found. hiveserver2 insert into the table
In fact, I wrote a large amount of base table data，But only hiveserver2 insert can be queried here.
When base.hive.auto-sync-data-write=true , the table record becomes consistent with the number of data inserted by hiveserver2.
Affects Versions
0.6.0
What engines are you seeing the problem on?
No response
How to reproduce
No response
Relevant log output
No response
Anything else
No response
Are you willing to submit a PR?
Code of Conduct