phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christine Feng (Jira)" <>
Subject [jira] [Updated] (PHOENIX-5432) Refactor LiteralExpression to use the builder pattern
Date Tue, 17 Dec 2019 01:30:00 GMT


Christine Feng updated PHOENIX-5432:
    Attachment: PHOENIX-5432.master.v11.patch

> Refactor LiteralExpression to use the builder pattern
> -----------------------------------------------------
>                 Key: PHOENIX-5432
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 4.15.0, 5.1.0
>            Reporter: Chinmay Kulkarni
>            Assignee: Christine Feng
>            Priority: Major
>         Attachments: PHOENIX-5432-master-v1.patch, PHOENIX-5432.master.v10.patch, PHOENIX-5432.master.v11.patch,
PHOENIX-5432.master.v2.patch, PHOENIX-5432.master.v3.patch, PHOENIX-5432.master.v4.patch,
PHOENIX-5432.master.v5.patch, PHOENIX-5432.master.v6.patch, PHOENIX-5432.master.v7.patch,
PHOENIX-5432.master.v8.patch, PHOENIX-5432.master.v9.patch, PHOENIX-5432.patch
>          Time Spent: 5h 40m
>  Remaining Estimate: 0h
> LiteralExpression is a mess. While it provides newConstant() APIs to build the object,
it also provides two public constructors. There are 10 overloaded newConstant() methods and
it is unclear which API to use in which case.
> This should be refactored to use the builder pattern and final member variables. Ideally,
getters such as getMaxLength() should be simple member variable accessors and other ad-hoc
logic surrounding those variables should be handled correctly when setting their respective

This message was sent by Atlassian Jira

View raw message