[
https://issues.apache.org/jira/browse/ASTERIXDB-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828548#comment-15828548
]
ASF subversion and git services commented on ASTERIXDB-1711:
------------------------------------------------------------
Commit 7ff91d02c6a535682fe05891c09f2e84efbce8d4 in asterixdb's branch
refs/heads/master from [~tillw]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=7ff91d0 ]
ASTERIXDB-1711: remove "Aql"
- AQLAPIServlet -> FullAPIServlet
- AqlPrimitiveValueProviderFactory -> PrimitiveValueProviderFactory
- remove AqlLogicalPlanAndMetadataImpl
- remore AqlMetadataImplConfig
Change-Id: I8e371941ba509d10193649aaed48a74a08d2d1f5
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1447
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
BAD: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: abdullah alamoudi <bamou...@gmail.com>
> Clean up class names
> --------------------
>
> Key: ASTERIXDB-1711
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1711
> Project: Apache AsterixDB
> Issue Type: Task
> Components: AsterixDB, Hyracks
> Reporter: Till
> Assignee: Till
>
> Some classes have names that include "AQL" (even though they are not language
> specific) or "Asterix" (even tough that's part of package names).
> We should aim to name classes based on their functionality and clean up class
> names that are not named that way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
