asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ASTERIXDB-2023) Introduce Enums instead of using bytes for ActiveEvents and Messages
Date Tue, 08 Aug 2017 11:46:00 GMT


ASF subversion and git services commented on ASTERIXDB-2023:

Commit 07075667c39d1b44939dfb83389de2626b21d8b7 in asterixdb's branch refs/heads/master from
[;h=0707566 ]

[ASTERIXDB-2008][CLUS] Only add pending removal if node known

[ASTERIXDB-2023][ING] Introduce Enums instead of using bytes

- user model changes: no
- storage format changes: no
- interface changes: no

- Only nodes which are known to cluster manager are added
to the list of nodes pending removal. Other nodes are ignored
- Enums introduced:
  - ActiveEvent.Kind
  - ActivePartitionMessage.Event
- Remove AdapterRuntimeManager
- Remove AdapterExecutor

Change-Id: I7044896559798426c04a3f46861bc5335b25d140
Tested-by: Jenkins <>
Integration-Tests: Jenkins <>
Reviewed-by: Murtadha Hubail <>

> Introduce Enums instead of using bytes for ActiveEvents and Messages
> --------------------------------------------------------------------
>                 Key: ASTERIXDB-2023
>                 URL:
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: ING - Ingestion
>            Reporter: Abdullah Alamoudi
>            Assignee: Abdullah Alamoudi
> Some classes such as ActiveEvent uses a byte member to indicates type. While this is
not incorrect, it introduces room for mistakes. In addition, logging becomes harder to follow
if the byte value is logged.

This message was sent by Atlassian JIRA

View raw message