Hi team, first time here. I have an issue when try...
# troubleshooting
i
Hi team, first time here. I have an issue when trying to update a table via API. The update is not being applied.
g
What do you mean by not being applied? Can you explain that a bit further? Given that beautiful Ñ in your surname, I’m going to assume you may also speak Spanish. Feel free to ask in Spanish if you feel more comfortable (I do, for sure 😆)
i
Hi @Gonzalo Ortiz. Yeah i speak spanish but lets keep English so everyone is able to understand my issue 😅. So i have a real time table, with 2 replication configured in the segment. It consume from kafka, so it includes the related configuration. Since one of our topic is used from another workflow as a sink topic of a kafka stream application using exactly once v2 semantics, It required to update the stream configuration of the realtime table isolation level. We perform the update through Pinot API. When we see logs, the configuration of the kafka consumer used by Pinot hasn't changed
m
Could you share the config you changed?
i
Copy code
"ingestionConfig": {
    "streamIngestionConfig": {
      "streamConfigMaps": [
        { *kafka stream configuration*
          "stream.kafka.isolation.level": "read_committed"
        }
      ]
    }
  },
m
Does the get api (or Pinot UI) show this as being set, or it is not even saved? If it does, then it should take effect from the next segment (or you can do a force commit). If it does not even show up, then it was likely rejected. Does the controller log show any message in this regard?
i
Controller log shows
Copy code
INFO [PinotTableRestletResource] [grizzly-http-server-2] Successfully updated table:
But no changes effects here
Copy code
INFO [ConsumerConfig] [table__16__5__20250626T2058Z] ConsumerConfig values: 
    *other configs*
	isolation.level = read_uncommitted
m
I meant in the table config (either via get api or via Pinot UI), do you see the new value or the old one?
l
The value is updated on the UI. The main issue we are facing is this one despite having the values correctly set on the UI.
👆 1
m
And even after a new segment for a partition is created? Also how are you validating it didn’t take effect?
l
it keeps spitting out that message unfortunatly
i
@Mayank yes, even after a new segment is created, it didn`t take effect