Apache Pinot

Hello :slightly_smiling_face:
Can someone remind me the steps to handle `"message": "MergeResponseError: Data schema mismatch between merged block:` after a REALTIME table backward-compatible schema change ? (new column)
I've tried `Reload All Segments`
Is that because I haven't set _`pinot.server.instance.reload.consumingSegment` ?_

_Full message:_
```[
  {
    "errorCode": 500,
    "message": "MergeResponseError:
Data schema mismatch between merged block: 

[communityId(STRING),documentId(STRING),eventTimeString(STRING),eventType(STRING),hoverDuration(INT),ibcustomer(STRING),origin(STRING),projectId(STRING),selectionId(STRING),timeString(STRING),userId(STRING)] 

and block to merge:

[communityId(STRING),documentId(STRING),eventTimeString(STRING),eventType(STRING),ibcustomer(STRING),origin(STRING),projectId(STRING),selectionId(STRING),timeString(STRING),userId(STRING)], 
drop block to merge"
  }
]```

Oh, I'd have to see with the SREs
Is that the only way ?

Because that would mean changing a schema would lead to downtime, right ?

hmm, typically it should be if it’s backwards compatible changes

Can you create an issue and describe how you find this issue?

-&gt; <https://github.com/apache/incubator-pinot/issues/7077> :slightly_smiling_face:

Yes, in order to reload consuming segment as well, you need to set a flag

We should consider making it on by default

<@UDT7GFEG6> Is there any benefit to keeping it off ?

I don’t think so. I think the flag is added when testing the feature

Okay
It's this flag : _`pinot.server.instance.reload.consumingSegment`_ , right ? :slightly_smiling_face:

Great news, I'll try that then :tada:
Thanks Jackie

<@UGRJA9TEH> PR to set the default behavior: <https://github.com/apache/incubator-pinot/pull/7078>