[ https://issues.apache.org/jira/browse/HBASE-18784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Busbey updated HBASE-18784: -------------------------------- Attachment: HBASE-18784-branch-1.v2.patch -branch-1 version of v2 - work around the lack-of refactoring that came into branch-2+ from the async wal - javadoc/checkstyle complaints from precommit This was different enough due to the differences between branch-1 and branch-2 that a quick additional review is needed, I think. > Use of filesystem that requires hflush / hsync / append / etc should query > outputstream capabilities > ---------------------------------------------------------------------------------------------------- > > Key: HBASE-18784 > URL: https://issues.apache.org/jira/browse/HBASE-18784 > Project: HBase > Issue Type: Improvement > Components: Filesystem Integration > Affects Versions: 1.4.0, 2.0.0-alpha-2 > Reporter: Sean Busbey > Assignee: Sean Busbey > Priority: Blocker > Fix For: 2.1.0, 1.5.0 > > Attachments: HBASE-18784-branch-1.v2.patch, HBASE-18784.0.patch, > HBASE-18784.1.patch, HBASE-18784.2.patch > > > In places where we rely on the underlying filesystem holding up the promises > of hflush/hsync (most importantly the WAL), we should use the new interfaces > provided by HDFS-11644 to fail loudly when they are not present (e.g. on S3, > on EC mounts, etc). -- This message was sent by Atlassian JIRA (v6.4.14#64029)