[jira] [Commented] (KUDU-577) Specification for expected semantics and client modes
[ https://issues.apache.org/jira/browse/KUDU-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142225#comment-16142225 ] Jean-Daniel Cryans commented on KUDU-577: - [~dr-alves] same question as Todd above. > Specification for expected semantics and client modes > - > > Key: KUDU-577 > URL: https://issues.apache.org/jira/browse/KUDU-577 > Project: Kudu > Issue Type: Sub-task > Components: api, client >Affects Versions: M4.5 >Reporter: Jean-Daniel Cryans >Assignee: David Alves >Priority: Critical > > We need a detailed description of what the different client modes are and > what it means the clients should do. This is to ensure that both terminology > and behavior match between languages. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KUDU-577) Specification for expected semantics and client modes
[ https://issues.apache.org/jira/browse/KUDU-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022119#comment-16022119 ] Todd Lipcon commented on KUDU-577: -- [~dralves] what's left to do on this? If there is no current action item here let's close the JIRA? > Specification for expected semantics and client modes > - > > Key: KUDU-577 > URL: https://issues.apache.org/jira/browse/KUDU-577 > Project: Kudu > Issue Type: Sub-task > Components: api, client >Affects Versions: M4.5 >Reporter: Jean-Daniel Cryans >Assignee: David Alves >Priority: Critical > > We need a detailed description of what the different client modes are and > what it means the clients should do. This is to ensure that both terminology > and behavior match between languages. -- This message was sent by Atlassian JIRA (v6.3.15#6346)