The following table lists known issues for Teradata Listener, by feature area:
Feature Area | Issue | Work Around |
---|---|---|
Autoshred default values for columns | Not inserted when data is absent in payload. | |
Autoshred with BLOB data type | Does not take more than 64000 bytes. | |
Elastic search limit | When elastic search limit is reached, error should be returned during source creation. | If you cannot find the source you created in the user interface, use the Get a Source REST API. |
HDFS storage | Ingested data stored even with invalid / blank password. | |
HDFS system creation | Invalid hostname returns success. | |
Insert JSON data | Cannot insert data beyond 64000 bytes. | |
QueryGrid and JDBC targets | When multiple JSON fields are mapped to one column, no error is returned and the target goes to starting state. | Contact customer support to request deletion of the target and writer through kubectl. Do not attempt to map multiple JSON fields to one column. |
MQTT source | When you edit an MQTT source using either the API or UI, the MQTT source goes to error state for 10 to 60 seconds. | Check status again in 60 seconds. |
QueryGrid target | When one JSON field is mapped to multiple columns, no error is returned and the target goes to starting state. | Contact customer support to request deletion of the target and writer through kubectl. Do not attempt to map one JSON field to multiple columns until a patch is provided. |
Table recreation | Unable to reconnect after table recreation. | Make sure you restart the writer. |
QueryGrid user shredding | After updating mapping for user shredding, the QueryGrid target goes to error mode. | Create a new target. |