In fact, not Vinod...
This was actually a configuration issue. Not a bug from EI side. Only issue
was that the issue was not apparent from the stack-trace.
I have changed the datasource name in analytics-datasources.xml, but missed
out updating the same at analytics-config.xml. That was the
Hi DilanA,
I'm not exactly clear about the issue. Is this something we need to fix in
the analytics distribution or because of your changes done in
analytics-datasources.xml?
If there is something we need to fix in EI, please raise a ticket with
label analytics in Github.
Thanks,
Vinod
Hi All,
I had an off-line discussion with Mohan on this and figured out the root
cause which was not obvious when looking at the stack-trace.
The issue was "Updating the analytics database names at
analytics-datasources.xml, but those changed names been not reflected at
analytics-config.xml".
Hi All,
Currently I am testing out a WSO2 EI Integrator cluster with analytics for
the on-going kubernetes-ei effort [1] [2]
The deployed pattern includes an EI Integrator profile cluster with one
analytics standalone node. In spite of the fact that I deploy this on a
kubernetes cluster (I am
