You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe:
Two data found during test.
When we analyze a table with 60 million rows and about 10 columns(with indexes), it costs 59s.
When we analyze a table with 10 million rows and about 369 columns(with indexes), it costs 3min.
It shows that when the number of columns increases, the analyze time is heavily increased.
Describe the feature you'd like:
We need to find a way to improve the analyze strategy for the wide table to make sure that we can get a tolerable execution time for a wide table. (We may analyze a table with hours when it's huge and wide)
Feature Request
Is your feature request related to a problem? Please describe:
Two data found during test.
When we analyze a table with 60 million rows and about 10 columns(with indexes), it costs 59s.
When we analyze a table with 10 million rows and about 369 columns(with indexes), it costs 3min.
It shows that when the number of columns increases, the analyze time is heavily increased.
Describe the feature you'd like:
We need to find a way to improve the analyze strategy for the wide table to make sure that we can get a tolerable execution time for a wide table. (We may analyze a table with hours when it's huge and wide)
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
The text was updated successfully, but these errors were encountered: