can I add partitioning to a table that is already ...
# troubleshooting
l
can I add partitioning to a table that is already existing/ingesting data? and can partitioning work by itself without the groupReplicas? would it speed up queries?
k
yes, existing segments wont benefit but new segments will use that information to speed up queries
👍 1
l
thank you! that would explain why old segments still seem to be slow
is that true for any kind of indexing?
m
Yes, this is true for any kind of indexing @Luis Fernandez. Availability of metadata/indexing is per segment, and query execution makes use of it as long as it is available.
k
I was about to say its not true 🙂 but I think there are multiple parts to your question
Most indexes will start showing performance improvements once you change the table config and invoke segment reload api on controller
m
Ah yes, there are multiple parts indeed. What I described in my previous response was a case where older segments did not have the desired index, and newer ones did. In that case, new segments will use the indexes. However, like @Kishore G mentioned, you can invoke segment reload api to rebuild indexes for existing segments as well.
🙌 1
l
in the UI that would be “Reload All Segments” right?
is that the same if I add partitioning?
also does partitioning for numPartitions does it have to match the number of partitions from kafka?
k
Partitioning does not really fall under indexing.. it can only be done during ingestion as of now