You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by "JiekerTime (via GitHub)" <gi...@apache.org> on 2023/05/31 07:20:52 UTC
[GitHub] [shardingsphere] JiekerTime opened a new issue, #25957: The meaning of broadcast table.
JiekerTime opened a new issue, #25957:
URL: https://github.com/apache/shardingsphere/issues/25957
I learned a lot of sub-table rules, among which the meaning of broadcast table makes me puzzled.
What is the meaning of its existence, is it a function of historical legacy？
----
I guessed some of its benefits, such as disaster tolerance, fast routing, and solving spanning query problems.
- about disaster tolerance:
When a database or a table goes down, this can lead to data inconsistency or even unavailability of the entire cluster. So this advantage is excluded.
- about fast routing
Is it really better than single table routing speed?
- about solving spanning query problems
Most associative queries are merged into the Proxy's memory, and by streaming merge, etc., I don't think this improves performance much, and is a waste of physical storage space.
---
I am really troubled and need help to clear the confusion
--
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: notifications-unsubscribe@shardingsphere.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] RaigorJiang commented on issue #25957: The meaning of broadcast table.
Posted by "RaigorJiang (via GitHub)" <gi...@apache.org>.
RaigorJiang commented on issue #25957:
URL: https://github.com/apache/shardingsphere/issues/25957#issuecomment-1579788095
Refer to https://shardingsphere.apache.org/document/current/en/features/sharding/concept/#broadcast-data-frame
The significance of the broadcast table is to facilitate join queries with big tables.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] JiekerTime commented on issue #25957: The meaning of broadcast table.
Posted by "JiekerTime (via GitHub)" <gi...@apache.org>.
JiekerTime commented on issue #25957:
URL: https://github.com/apache/shardingsphere/issues/25957#issuecomment-1584216601
> Refer to https://shardingsphere.apache.org/document/current/en/features/sharding/concept/#broadcast-data-frame
>
> The significance of the broadcast table is to facilitate join queries with big tables.
As a user, is this perception obvious? Broadcast table data volume should be very small, I do not think the cross-library query will have significant performance improvement, compared to a single table I think the storage resources are more economical, is not it.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org