beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <>
Subject [jira] [Updated] (BEAM-1281) GlobalWindow needs non-empty encoding in nested context
Date Thu, 19 Jan 2017 03:08:26 GMT


Kenneth Knowles updated BEAM-1281:
    Priority: Minor  (was: Critical)

> GlobalWindow needs non-empty encoding in nested context
> -------------------------------------------------------
>                 Key: BEAM-1281
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: Minor
> One easy motivation: as a StateNamespace, the global window's stringKey ends up being
is "//" while the global namespace's stringKey is "/". As paths, these are identical, though
we don't currently treat them as paths, quite. It isn't clear whether this is desirable. Maybe
it is harmless but it complicates parsing and interpretation.
> For a system that actually builds hierarchical paths out of, say, some prefix, the StateNamespace,
and a subsequent ID, the canonicalized path is the same so it is not possible to deserialize
to the original.

This message was sent by Atlassian JIRA

View raw message