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
There are multiple ways how this could be implemented, namely:
Instead of/Beyond the existing configuration option "stream.pulsar.topic.name": "pulsar-test" we could have something like "stream.pulsar.topic.names": [ "pulsar-test-1", "pulsar-test-2"].
Beyond the above existing configuration option we could have something like "stream.pulsar.topic.pattern": "pulsar-test-*" where the pattern adheres to standard regex rules.
We could support such pattern-like inputs in the existing configuration option, e.g. an input field like "stream.pulsar.topic.name": "persistent://some_tenant/some_namespace/*" should make Pinot bind a real-time table to all topics under the given tenant/namespace.
Another alternative solution would be the capability of binding multiple topics to the same real-time table by sending subsequent requests to the Pinot Server (e.g., first, creating some_table as a real-time one and providing topic A as its source, however, a subsequent real-time table request with the name some_table and topic B would just subscribe to B and direct the corresponding flow into some_table, as well).
The text was updated successfully, but these errors were encountered:
any progress on this? I'm in a position where I'm creating multiple pulsar topics with the same schema and we need to have it in one table instead of one per topic.
There are multiple ways how this could be implemented, namely:
"stream.pulsar.topic.name": "pulsar-test"
we could have something like"stream.pulsar.topic.names": [ "pulsar-test-1", "pulsar-test-2"]
."stream.pulsar.topic.pattern": "pulsar-test-*"
where the pattern adheres to standard regex rules."stream.pulsar.topic.name": "persistent://some_tenant/some_namespace/*"
should make Pinot bind a real-time table to all topics under the given tenant/namespace.Another alternative solution would be the capability of binding multiple topics to the same real-time table by sending subsequent requests to the Pinot Server (e.g., first, creating
some_table
as a real-time one and providing topicA
as its source, however, a subsequent real-time table request with the namesome_table
and topicB
would just subscribe toB
and direct the corresponding flow intosome_table
, as well).The text was updated successfully, but these errors were encountered: