[
https://issues.apache.org/jira/browse/ASTERIXDB-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570479#comment-15570479
]
ASF subversion and git services commented on ASTERIXDB-1673:
------------------------------------------------------------
Commit e65a57ab27a92670f9ef42d188c1b62a11fe765d in asterixdb's branch
refs/heads/master from [~wyk]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=e65a57a ]
ASTERIXDB-1673 and some small cleanups
- Fix potential object creation issue in ARecordCaster.
- refactor getFieldOffsetById() in ARecordSerializerDeserailzer.
- remove dead code in method set() in ARecordVisitablePointable.
- Introduce unrestable allocation in PointableAllocator as static method.
Change-Id: I3802a5a33b46b58967ffb4a28a70ebe9671bfabf
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1260
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Yingyi Bu <[email protected]>
> ARecordCaster potential object creation problem
> -----------------------------------------------
>
> Key: ASTERIXDB-1673
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1673
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: AsterixDB, Data Model
> Reporter: Wail Alkowaileet
> Assignee: Wail Alkowaileet
> Priority: Trivial
>
> I use ACastVIsitor extensively in my work and I found that on
> loadRequiredType:
> The allocator will keep allocating Pointables (for typetag and fieldNames)
> which would never be cleared.
> I ran an experiment and got more than 6 million objects on a dataset of size
> 1.5GB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
