[
https://issues.apache.org/jira/browse/MESOS-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haosdent updated MESOS-3350:
----------------------------
Description:
Currently we use string to store mesos version in protobuf. In
[MESOS-1841-reviews|https://reviews.apache.org/r/37024/], [~marco-mesos] think
it would be better to create a protobuf struct which named VersionInfo like:
{code}
message VersionInfo {
option string git_sha = 1;
option string build_user = 2;
xxxxx
}
{code}
So that we could use this struct everywhere (expose informations to http
endpoint, replace the version string in MasterInfo).
was:
Currently we use string to store mesos version in protobuf. In
[|https://reviews.apache.org/r/37024/] It would be better to create a protobuf
struct which named VersionInfo like:
{code}
message VersionInfo {
option string git_sha = 1;
option string build_user = 2;
xxxxx
}
{code}
So that we could use this struct everywhere (expose informations to http
endpoint, replace the version string in MasterInfo).
> Create a protobuf VersionInfo to store mesos version information
> ----------------------------------------------------------------
>
> Key: MESOS-3350
> URL: https://issues.apache.org/jira/browse/MESOS-3350
> Project: Mesos
> Issue Type: Improvement
> Reporter: haosdent
> Assignee: Marco Massenzio
> Labels: tech-debt
>
> Currently we use string to store mesos version in protobuf. In
> [MESOS-1841-reviews|https://reviews.apache.org/r/37024/], [~marco-mesos]
> think it would be better to create a protobuf struct which named VersionInfo
> like:
> {code}
> message VersionInfo {
> option string git_sha = 1;
> option string build_user = 2;
> xxxxx
> }
> {code}
> So that we could use this struct everywhere (expose informations to http
> endpoint, replace the version string in MasterInfo).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
