exceptionTrace is not activated. #11170
Comments
|
Thank you for pointing out the configuration error. To address this issue, I will modify the existing table and schema files. Based on your feedback, it seems that changing the incorrect table name ( If there are any further issues, please let me know. |
|
I need some other help. We are using version 1.0.0 of pinot and are operating in hybrid mode of QuickStartCluster.
|
|
The segment might not be saved correctly due to the schema change. Try using the Reload Table Segments API to reload table segments. These actions can be done with the Swagger Pinot Controller API. |
|
I've tried reloading segments, rebalance servers, and deleting and regenerating segments, but all I get is a message that the segment is not normal.
|
|
I am not sure if the segment was deleted properly because the segment name is the same. These are some solution with more details delete segment
If you need to restore realtime segmenthttps://www.markhneedham.com/blog/2021/12/06/apache-pinot-copy-segment-new-table/
|
|
Thanks for your guide. Like your guide, I proceeded as follows. 
However, segment errors continued to occur. 
|
|
I've never seen a case like this before. I'll check pinot issue to see if there are any similar issues. If you have any logs, please share them with me. |
|
my pinot verision : 1.0.0 This is the script used to insert the 3.0.0 version table. All tables except exceptionTrace are normal and data collection is working well.
|
|
While testing, I checked the log below. Would this help?
|
|
exceptionTrace table uses CLP encoding. I am not sure CLP library support Graviton(ARM64). reference: Pinot doesn't provide official binaries for M1 or M2 Mac systems. |
|
Thanks for your help. Perhaps CLP does not support arm64 architecture. |
|
I'm glad to hear that the issue has been resolved. Apache Pinot utilizes the According to the issue linked below, it appears that there are plans to support binaries for multiple platforms, including aarch64, in the near future: |
|
It seems that Apache Pinot is also planning to support various platform, including aarch64. |
|
The issue of not being able to find the exceptionTraceV1 table seems to be a problem with version 3.0.0. The table schema specifies it as exceptionTrace, but it was using the previous table name exceptionTraceV1, causing this issue. Upgrading to version 3.0.1 should resolve this issue. I believe this information should have been included in the release notes for 3.0.1 :)
|
I am setting version 3.0.0.
However, an error occurred while creating the exceptionTrace table in pinot.
It was confirmed that the schemaName was incorrect, and the table was applied after correction.
pinot admin confirmed that the status was not normal as shown in the picture below.
The text was updated successfully, but these errors were encountered: