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

Fabian Hueske resolved FLINK-846.
---------------------------------
    Resolution: Implemented

Implemented in de8e066ccbd0a31e5746bc0bee524a48bba3a552

> Semantic Annotations - Inconsistencies
> --------------------------------------
>
>                 Key: FLINK-846
>                 URL: https://issues.apache.org/jira/browse/FLINK-846
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: GitHub Import
>            Assignee: Fabian Hueske
>              Labels: github-import
>             Fix For: pre-apache
>
>
> This is basically a thread for discussion. There are still a few 
> inconsistencies in the semantic annotations. The following examples 
> illustrate that:
> _Constant fields_:
> `"1 -> 0,1" "3->4"`  means field 1 is copied unmodified to 0 and 1, while 3 
> becomes 4.
> `"1 ->0,1 ; 3->4"`   means the same thing, expressed in a single string 
> (semicolon is the delimiter between statements about fields).
> `"1 , 3"` means that 1 and 3 remain constant as 1 and 3. Note that comma is 
> the delimiter here.
> _Read Fields_:
> `"0 , 2"` means that fields 0 and 2 are read. Note that here, the delimiter 
> is the comma, like with the standalone constant fields, unlike the constant 
> fields with arrow notation.
> I find that a bit inconsistent, especially the mixed use of comma and 
> semicolon for the constant fields.
>   - Do we want to keep it that way?
>   - Or use the  semicolon for the standalone constant fields and read fields?
>   - Or use the comma in the constant fields (finding an alternative delimiter 
> for the right hand side of the arrow?
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/stratosphere/stratosphere/issues/846
> Created by: [StephanEwen|https://github.com/StephanEwen]
> Labels: 
> Created at: Wed May 21 20:54:26 CEST 2014
> State: open



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to