-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Pinot Tables #11332
Comments
I had start Apache Zookeeper, Pinot Controller, Pinot Broker, and Pinot Server.(https://docs.pinot.apache.org/basics/getting-started/running-pinot-locally) |
@donghun-cho please review this issue. |
The pinot table won't be created if pinot cluster cannot connect to Kafka or cannot find the kafka topic. can the pinot cluster access kafka? |
Thank you for your clarification. Two Kafka services were started locally, and one was shut down to solve the problem. |
This applies to realtime table only A Pinot Minion is also required for hybrid tables. https://docs.pinot.apache.org/operators/operating-pinot/pinot-managed-offline-flows |
Using API/brokers/tables to view tables, systemMetricDouble does not exist, but executing point-admin.sh addTable yields an error |
https://docs.pinot.apache.org/basics/concepts/components/table#offline-table-creation |
Could you check which table (realtime or offline) has been created? |
try using curl to create realtime. or delete systemMetricDouble schema and offline table and recreate tables by following steps
|
Using Pinpoint's built-in Kafka and switching to Apache Kafka resulted in the issue |
First of all, thank you very much for your patient answer. After replacing my deployed Kafka with pinpoint-admin.sh Kafka, I followed your advice and recreated the real-time table using script and the offline table using curl. Pinot successfully created the table. The only thing I don't quite understand is why my self built Kafka failed |
@Alberter It seems that I have resolved the issue. The root cause was that the "stream.kafka.broker.list" port in the pinot-inspector-stat-application-realtime-table.json file should be changed from 19092 to 9092. Also, please try running the curl command. |
No, because the application table uses Pinot ingestion aggregations and already has good response times compared to the agent table |
When I use the script multi table. sh to create the pinot table, an error of 500 is reported
The text was updated successfully, but these errors were encountered: