falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "pavan kumar kolamuri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1607) Code refactoring: Refactor ID into more specific sub classes
Date Thu, 19 Nov 2015 05:06:11 GMT

    [ https://issues.apache.org/jira/browse/FALCON-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012806#comment-15012806

pavan kumar kolamuri commented on FALCON-1607:

[~ajayyadava]  I understand you concern. But https://issues.apache.org/jira/browse/FALCON-1234
is pending from longtime and it is huge patch. Small changes also requires lot of time to
address as it involves lot of test cases. I will be happy to help you in re-basing this patch
after state-store

> Code refactoring: Refactor ID into more specific sub classes
> ------------------------------------------------------------
>                 Key: FALCON-1607
>                 URL: https://issues.apache.org/jira/browse/FALCON-1607
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Ajay Yadava
>            Assignee: Ajay Yadava
>            Priority: Critical
>             Fix For: trunk
>         Attachments: FALCON-1607.patch
> Currently the file ID.java is used to uniquely identify various "entities" for native
scheduler. This class is overloaded and serves multiple tasks like getting an entity id for
an entity and an instance id for an instance. Keeping all this code in one class creates various
issues like no check on object creation - one can accidentally call an instance id when the
underlying object was supposed to be  representing an entity etc. Since ID represents the
unique identifier for an instance, entity etc. most methods pass ID and this makes the code
hard to reason as we don't know what are we dealing with - an entity or an instance or something

This message was sent by Atlassian JIRA

View raw message