nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mr TheSegfault (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (MINIFICPP-622) Transmit binary information for CAPI implementations in heartbeat
Date Wed, 17 Jul 2019 15:36:00 GMT

     [ https://issues.apache.org/jira/browse/MINIFICPP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mr TheSegfault reassigned MINIFICPP-622:
----------------------------------------

    Assignee: Daniel Bakai

> 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: Mr TheSegfault
>            Assignee: Daniel Bakai
>            Priority: Major
>              Labels: CAPI, nanofi
>             Fix For: 0.7.0
>
>
> 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
(v7.6.14#76016)

Mime
View raw message