BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [453]':
Is back to normal.
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [452]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/452/";>PLC4X/PLC4X/develop
[develop] [452]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [451]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/451/";>PLC4X/PLC4X/develop
[develop] [451]"
Hi all,
Well, you get PlcValues from the response that wrap the different datatypes. So
generally you shouldn't care about the detail type.
However, you can call getObject() which returns the core value the plc-value
has ... so if it's the PLCValue for a Short, getObject will return a short
va
So, you are generating the schema yourself, such that downstream if they
inherit schema they will just get what you generate? And you are trying to do
that by the connection string? If so, a different way I could imagine doing
would be to get the ’types’ of the data from the responses themselv
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [450]':
Is back to normal.
Hi Inigo,
Thanks for this very thorough explanation. It really helps understand NiFi and
the concepts a lot more this way. Thank you for your hard work and your
willingness to contribute this back :-)
We documented the process of contributing here:
https://plc4x.apache.org/developers/contribut
BUILD-UNSTABLE: Job 'PLC4X/PLC4X/develop [develop] [449]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/449/";>PLC4X/PLC4X/develop
[develop] [449]"
Hi Chris, Otto,
Regarding the Record Processor concept, i will try to give an overview. In
Nifi, information packages are called Flowfiles, and these are the actual units
of information that are exchanged between Procesors, all along the dataflow.
Flowfiles have two sections where we can manage
