You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Arpad Boda (Jira)" <ji...@apache.org> on 2021/03/01 20:08:00 UTC
[jira] [Updated] (MINIFICPP-622) Transmit binary information for
CAPI implementations in heartbeat
[ https://issues.apache.org/jira/browse/MINIFICPP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpad Boda updated MINIFICPP-622:
---------------------------------
Fix Version/s: (was: 0.9.0)
nanofi
> Transmit binary information for CAPI implementations in heartbeat
> -----------------------------------------------------------------
>
> Key: MINIFICPP-622
> URL: https://issues.apache.org/jira/browse/MINIFICPP-622
> Project: Apache NiFi MiNiFi C++
> Issue Type: New Feature
> Reporter: Marc Parisi
> Priority: Major
> Labels: CAPI, nanofi
> Fix For: nanofi
>
>
> Heartbeats transmit a great deal of information as per our defined spec: [https://cwiki.apache.org/confluence/display/MINIFI/C2+Design+Proposal]
> This ticket will be responsible for figuring out what can and cannot be sent via these binaries created using the CAPI
>
> For CAPI : probably need the AgentBuild information, but also potentially information from a consumer's program – is there a way to capture information about THEIR binary information
>
> May include information like python version, GCC version, etc that's NOT about our library ( and not captured in AgentBuild) – but rather about theirs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)