dang-stripe opened a new issue, #15440:
URL: https://github.com/apache/pinot/issues/15440
We ran into this error while restarting servers to reload segments. This
caused the servers to fail to startup.
```
[2025-04-01 20:24:22.723960] ERROR
[example_table_v1_OFFLINE-OfflineTableDataManager]
[HelixTaskExecutor-message_handle_thread_4:155] Failed to load existing
segment: example_table_v1_1989 with CRC: 3623618827 on tier: default
[2025-04-01 20:24:22.724033] java.lang.RuntimeException: Attempt to
re-create an existing index for key: reporting_week.forward_index, for
segmentDirectory:
/pinot/data/index/example_table_v1_OFFLINE/example_table_v1_1989/v3
[2025-04-01 20:24:22.724062] at
org.apache.pinot.segment.local.segment.store.SingleFileIndexDirectory.checkKeyNotPresent(SingleFileIndexDirectory.java:197)
~[pinot-all-1.2.0-2025-02-12-8fe105e2b7-SNAPSHOT-jar-with-dependencies.jar:1.2.0-2025-02-12-8fe105e2b7-SNAPSHOT-8fe105e2b707ef1a6ca00f9fd546259ad88114c4]
[2025-04-01 20:24:22.724106] at
org.apache.pinot.segment.local.segment.store.SingleFileIndexDirectory.allocNewBufferInternal(SingleFileIndexDirectory.java:170)
~[pinot-all-1.2.0-2025-02-12-8fe105e2b7-SNAPSHOT-jar-with-dependencies.jar:1.2.0-2025-02-12-8fe105e2b7-SNAPSHOT-8fe105e2b707ef1a6ca00f9fd546259ad88114c4]
[2025-04-01 20:24:22.724134] at
org.apache.pinot.segment.local.segment.store.SingleFileIndexDirectory.newBuffer(SingleFileIndexDirectory.java:138)
```
This happened after applying a table change that adding new derived columns
and adding the derived column to the `dimensionsSplitOrder` of the startree
index.
table config transform
```
{
"columnName": "reporting_week",
"transformFunction": "dateTrunc('WEEK', reporting_date)"
},
```
schema
```
{
"name": "reporting_week",
"dataType": "TIMESTAMP",
"notNull": false,
"format": "TIMESTAMP",
"granularity": "1:DAYS"
},
```
We found that setting `enableDynamicStarTreeCreation` to true bypassed this
error and let the servers recover.
cc @Jackie-Jiang
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
