So I think this is actually an OODT bug, sending to OODT and CC to DRAT.
so @imesha i think the issue is here
9:55 PM
you actually don’t allow override of the client factory at runtime since at
this line in RpcCommFactory for workflow
9:55 PM
https://github.com/apache/oodt/blob/master/work
Sounds good to me. Should also increase the release cadence as well.
On 5 October 2019 at 09:06:35, Chris Mattmann (mattm...@apache.org) wrote:
Here is my suggested Roadmap here:
2.0 – first release where we remove all the Xml-RPC and we change nothing
else. Avro is the default, and only
comm
Here is my suggested Roadmap here:
2.0 – first release where we remove all the Xml-RPC and we change nothing else.
Avro is the default, and only
comm option – though interface exists for anyone that wants to roll their own.
We change nothing else*
2.1 – first release with newer JDK suppo
On 5 October 2019 at 11:25:41, Imesha Sudasingha (ime...@apache.org) wrote:
I think there was a plan to
remove XML rpc support completely and use avro only in 2.0.
That is true. XMLRPC needs to die.
Not sure about Knative, but certainly a Kubernetes operator would be
something interesting to l
Hi Tom,
Yes. That's pretty much all we planned for 2.0. I think there was a plan to
remove XML rpc support completely and use avro only in 2.0.
May be in 2.x something, we can see the possibility of your knative
suggestion and a more advanced kubernetes support?
Imesha
On Sat, 5 Oct 2019 at 15:
Alrighty with 1.9 shipped we can now look at 2.0 with all new fun stuff.
I’ve probably forgotten some bits and pieces but here’s my wish list:
React components and Breno’s wrapper for OpsUI and improved custom web app
embedding
Updating lots of old dependencies to more current stuff.
Newer JDK sup
