thatran opened a new issue, #10694:
URL: https://github.com/apache/pinot/issues/10694
Simply trying to add a realtime table to pinot where the table config json
includes this:
```
"ingestionConfig": {
"streamIngestionConfig": {
"streamConfigs": [
{
"realtime.segment.flush.threshold.rows": "0",
"stream.kafka.decoder.prop.format": "JSON",
"bootstrap.servers": "<EC2_HOST1>:9092",
"key.serializer":
"org.apache.kafka.common.serialization.ByteArraySerializer",
"stream.kafka.decoder.class.name":
"org.apache.pinot.plugin.inputformat.json.JSONMessageDecoder",
"streamType": "kafka",
"value.serializer":
"org.apache.kafka.common.serialization.ByteArraySerializer",
"stream.kafka.consumer.type": "LOWLEVEL",
"realtime.segment.flush.threshold.segment.size": "200M",
"stream.kafka.broker.list": "<EC2_HOST_1>:9092",
"realtime.segment.flush.threshold.time": "24h",
"stream.kafka.consumer.factory.class.name":
"org.apache.pinot.plugin.stream.kafka20.KafkaConsumerFactory",
"stream.kafka.consumer.prop.auto.offset.reset": "smallest",
"stream.kafka.topic.name": "test_topic"
}
]
},
```
fails, with the following api response:
```
{
"code": 400,
"error": null
}
```
In the pinot controller logs, the only related log messages are these:
```
2023/04/27 17:05:37.368 INFO [PinotTableRestletResource]
[grizzly-http-server-2] null exception: null
2023/04/27 17:05:37.368 INFO [ControllerResponseFilter]
[grizzly-http-server-2] Handled request from <REDACTED_IP> POST
https://<PINOT_HOST>:443/tables, content-type application/json status code 400
Bad Request
```
which basically provides no useful information.
**ISSUE: In the logs, there should be _some_ piece of information
logged/provided that helps to identify the problem cause.**
As shown above, there is none.
Here, the problem cause was a misconfiguration, it should have been
```
"ingestionConfig": {
"streamIngestionConfig": {
"streamConfigMaps": [
...
```
instead of
```
"ingestionConfig": {
"streamIngestionConfig": {
"streamConfigs": [
...
```
--
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]
