Issues
- Lineage call Scans run_records table which is extremely slow.CDAP-21145
- Restrict Re-Deployment of Replication PipelineCDAP-21127
- Multiple instances of pipeline getting triggered on scheduleCDAP-21122Resolved issue: CDAP-21122Vaibhav Sethi
- Preview not working for in internal auth enabled enterprise 6.11.0 instancesCDAP-21118Resolved issue: CDAP-21118Sidhdi Renge
- DPAL - ConnectionHandler logs not visible in Logs ExplorerCDAP-21117Resolved issue: CDAP-21117Sanket Sahu
- Set audit logs event in SecurityRequestContext/AuthenticationChannelHandler according to netty-http request flowCDAP-21085Resolved issue: CDAP-21085Sanket Sahu
- Appfabric service failing to start because of AuditLogSubscriberServiceCDAP-21084Resolved issue: CDAP-21084Sanket Sahu
- Scheduled pipelines not triggering in latest CDAP version (6.11.0-SNAPSHOT)CDAP-21068Resolved issue: CDAP-21068Avinash Achar
- Decrecate or Re-evaluate HBASE PLUGIN in hydrator plugins after Hadoop3 upgradeCDAP-21052Deepinder Dhuria
- Decrecate or Re-evaluate CASSANDRA PLUGIN in hydrator plugins after Hadoop3 upgradeCDAP-21051Deepinder Dhuria
- Decrecate or Re-evaluate CDAP-SENTRY auth module after hadoop3 upgradeCDAP-21050Deepinder Dhuria
11 of 11
Triggered pipeline fails with logs:
The token is written by
io.cdap.cdap.metadata.MetadataSubscriberService.WorkflowProcessor#processMessageand read fromio.cdap.cdap.internal.app.runtime.schedule.trigger.TriggerInfoContext#getWorkflowToken.If the pipeline is triggered before token is updated by metadata service, it fails.