Subscription when using data-index with postgresql

[Diogo]

Hi all,

I want to use the subscription function of data-index while using postgresql, but I'm getting this error:

I would like to know if this function in data-index graphiql is possible to use with postgresql or if, like the error that is throwing up is saying if it's not possible to be working with postgresql...

Thanks in advance.

Best Regards,

Diogo

[Cristiano Nicolai]

Hi Diogo,

Yeah, that's currently a limitation from the Data Index PostgreSQL implementation. Would you mind describing your use case so we can evaluate how to tackle this issue?

Thanks

--
You received this message because you are subscribed to the Google Groups "Kogito development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kogito-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kogito-development/e1f758ae-b3d3-412f-81f4-428be96ca84cn%40googlegroups.com.

--

Best regards,

Cristiano Nicolai

[Diogo]

Hi Cristiano,

Thanks a lot again for the quick response!

Is there any plans to get the subscription working with the postgresql persistence?

About the use case, we need to subscribe to the data-index to know the state of the workflows at any given point in time. But we don't want to do a query only from time to time to retreive the data, hence the subscription would be a good solution. Also, we are using data-index with postgresql because we already have a postgresql database, so it doesn't make much sense to have another database only for the kogito data-index.

I know that there are also the kafka messages produced every time a workflow changes is state, but from what I understood the data that comes in those messages can be changed in the future making our project to fail, so we would like to skip that road as well.

Best regards,

Diogo

[Cristiano Nicolai]

Hi Diogo,

Actually, that was going to be my suggestion, if you need a reliable way to get notification about process changes, I would recommend using the messaging events from the runtime ( Kafka ). That's the same source of events that is used by Data Index, the format is based on CloudEvents and yes that could be small changes in there but I think is most likely to be adding content but definitely, something that will be there in the long term.

From my perspective, Subscription is really more towards a UI thing as a WebSocket/SSE mechanism, it's not intended to guarantee delivery.

To view this discussion on the web visit https://groups.google.com/d/msgid/kogito-development/31158d80-b53e-4f45-b403-d977eb86a4f8n%40googlegroups.com.

[Diogo]

Hi Cristiano, 

Thanks a lot for your input, I think we will try a solution that involves both the kafka messages and the data-index graphiql.

Keep up the excelent work that you are doing with kogito!

Best regards,

Diogo