Known Issues by Feature Area - Teradata Listener

Teradata® Listener™ User Guide

Product
Teradata Listener
Release Number
2.04
Published
November 2018
Language
English (United States)
Last Update
2018-12-20
dita:mapPath
qin1538418638881.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-2910
lifecycle
previous
Product Category
Analytical Ecosystem
The following table lists known issues for Teradata Listener, by feature area:
Feature Area Issue Work Around
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 password.  
Insert JSON data Cannot insert data beyond 64000 bytes.  
Logs Each log appears to be selectable for more information, but nothing more appears when a log is selected. All available log information appears under each log title.
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.
Source If the source contains dead-letter records, only administrators can view source details in the UI. Use the API to retrieve dead-letter records.
Table recreation Unable to reconnect after table recreation. Make sure you restart the writer.
Target, bad records If there are more than 50 bad records, only the first 50 records can be retrieved from the UI. Use the Retrieve Dead-Letter Records REST API to retrieve all bad records.
Target, manual mapping If the database column names are different from the Listener metadata field names, the To Target fields in Custom Mapping are not prepopulated in the UI. Select the appropriate columns from the To Target list.
Target, user shred Unable to update user shred target table in System Connection in the UI. Recreate target with new table.