[ 
https://issues.apache.org/jira/browse/ASTERIXDB-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061380#comment-16061380
 ] 

ASF subversion and git services commented on ASTERIXDB-1953:
------------------------------------------------------------

Commit e0cf970124baed319800d58d107c4bfbe98ae84a in asterixdb's branch 
refs/heads/master from [~alamoudi]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=e0cf970 ]

[ASTERIXDB-1953][STO] Cleanup LSM File Managers

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

Details:
- use FileReference instead of String absolute path
- user error codes

Change-Id: I97bab76888790ca282ad9508ce8416f7c7a52fb7
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1849
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
BAD: Jenkins <[email protected]>
Reviewed-by: Ian Maxon <[email protected]>


> Clean LSM File Managers
> -----------------------
>
>                 Key: ASTERIXDB-1953
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1953
>             Project: Apache AsterixDB
>          Issue Type: Bug
>            Reporter: Abdullah Alamoudi
>            Assignee: Abdullah Alamoudi
>
> Currently, LSM File managers store all the paths as absolute path Strings. 
> This makes the code bug prone, and requires constructing multiple File 
> objects. and using the IO manager to resolve the io device.
> More over, all the error messages in these classes are outdated and use the 
> old mechanism of creating error messages.
> Instead of using absolute path strings, we should use FileReferences.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to