You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2014/05/06 04:02:16 UTC
[jira] [Updated] (AURORA-379) Deprecate Identity struct in
api.thrift
[ https://issues.apache.org/jira/browse/AURORA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Farner updated AURORA-379:
-------------------------------
Description:
Converting TODO into a ticket. Deprecate Identity struct in api.thrift.
There are 2 uses of this struct in TaskConfig and TaskQuery.
a) In TaskConfig, I think we should replace owner, environment and jobName fields with JobKey.
b) For TaskQuery, we can drop the owner field entirely. However, we will loose the ability to query all tasks by owned by a role and launched by a user. The simplest way forward seems to be add a user field to TaskQuery struct and remove the owner field.
Does that sound like a good way forward?
was:
Converting TODO into a ticket. Deprecate Identity struct in api.thrift.
[~wfarner] There are 2 uses of this struct in TaskConfig and TaskQuery.
a) In TaskConfig, I think we should replace owner, environment and jobName fields with JobKey.
b) For TaskQuery, we can drop the owner field entirely. However, we will loose the ability to query all tasks by owned by a role and launched by a user. The simplest way forward seems to be add a user field to TaskQuery struct and remove the owner field.
Does that sound like a good way forward?
> Deprecate Identity struct in api.thrift
> ---------------------------------------
>
> Key: AURORA-379
> URL: https://issues.apache.org/jira/browse/AURORA-379
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
> Reporter: Suman Karumuri
> Assignee: Suman Karumuri
>
> Converting TODO into a ticket. Deprecate Identity struct in api.thrift.
> There are 2 uses of this struct in TaskConfig and TaskQuery.
> a) In TaskConfig, I think we should replace owner, environment and jobName fields with JobKey.
> b) For TaskQuery, we can drop the owner field entirely. However, we will loose the ability to query all tasks by owned by a role and launched by a user. The simplest way forward seems to be add a user field to TaskQuery struct and remove the owner field.
> Does that sound like a good way forward?
--
This message was sent by Atlassian JIRA
(v6.2#6252)