Nivethika Mahasivam
Nivethika Mahasivam
Thanks for sharing @phydiux . I had the same experience. Using native-api resolves the issue. My solution here ``` declare var window: any; .... return new Promise((resolve, reject) => {...
@OneCricketeer @raphaelhamonnais Thanks for this detailed explanation. Could you also tell how exactly did you configure the heap size for the connector? Is configuring KAFKA_HEAP_OPTS with the required memory enough?...
Thank you very much both of you. It works now.
@rocketsciencenerd @yatharthranjan Based on what I noticed, it looks like the app works with .conf only. Currently the app uses the ComParE_2016.conf and it works fine. However, it crashes for...
Right. Currently, a similar configuration used per source-type to decide DISCONNECTED state per source-type. If that would be relevant here as well, we should probably put these configurations in one...
**Update on Storage** I worked on activating the cold storage for the platform. I integrated an adapted HDFS Connector to write key and value data of messages to HDFS. As...
isn't it already supported by specifications? Plus this should be reported under RADAR-Schemas?
I don't think the ids are shared if the same sequence-generator is used by many persistent entities.
Query parameter for detail sounds good. However, the reason for the API with list of `source-ids` is to retrieve data of sources that are recorded in MongoDB, but not currently...
Apparently, this is on purpose for security purposes. If necessary we can implement this. But the jhipster suggests to login again.