[jira] [Updated] (HBASE-21020) Determine WAL API changes for replication

2019-01-22 Thread Josh Elser (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Elser updated HBASE-21020:
---
  Resolution: Fixed
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

Thanks for the patch, Ankit!

> Determine WAL API changes for replication
> -
>
> Key: HBASE-21020
> URL: https://issues.apache.org/jira/browse/HBASE-21020
> Project: HBase
>  Issue Type: Sub-task
>  Components: wal
>Reporter: Josh Elser
>Assignee: Ankit Singhal
>Priority: Major
> Fix For: HBASE-20952
>
> Attachments: HBASE-21020.HBASE-20952.001.patch, 
> HBASE-21020.HBASE-20952.002.patch, HBASE-21020.HBASE-20952.003.patch, 
> HBASE-21020.HBASE-20952.004.patch, HBASE-21020.HBASE-20952.005.patch, 
> HBASE-21020.HBASE-20952.007.patch
>
>
> Spin-off of HBASE-20952.
> Ankit has started working on what he thinks a WAL API specifically for 
> Replication should look like. In his own words:
> {quote}
> At a high level, it looks,
>  * Need to abstract WAL name under WalInfo instead of Paths
>  * Abstract the WalEntryStream for FileSystem and Streaming system.
>  * Build WalStorage APIs to abstract operation on Wal.
>  * Provide the implementation of all above through corresponding WalProvider
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HBASE-21020) Determine WAL API changes for replication

2019-01-18 Thread Josh Elser (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Elser updated HBASE-21020:
---
Attachment: HBASE-21020.HBASE-20952.007.patch

> Determine WAL API changes for replication
> -
>
> Key: HBASE-21020
> URL: https://issues.apache.org/jira/browse/HBASE-21020
> Project: HBase
>  Issue Type: Sub-task
>  Components: wal
>Reporter: Josh Elser
>Assignee: Ankit Singhal
>Priority: Major
> Fix For: HBASE-20952
>
> Attachments: HBASE-21020.HBASE-20952.001.patch, 
> HBASE-21020.HBASE-20952.002.patch, HBASE-21020.HBASE-20952.003.patch, 
> HBASE-21020.HBASE-20952.004.patch, HBASE-21020.HBASE-20952.005.patch, 
> HBASE-21020.HBASE-20952.007.patch
>
>
> Spin-off of HBASE-20952.
> Ankit has started working on what he thinks a WAL API specifically for 
> Replication should look like. In his own words:
> {quote}
> At a high level, it looks,
>  * Need to abstract WAL name under WalInfo instead of Paths
>  * Abstract the WalEntryStream for FileSystem and Streaming system.
>  * Build WalStorage APIs to abstract operation on Wal.
>  * Provide the implementation of all above through corresponding WalProvider
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HBASE-21020) Determine WAL API changes for replication

2018-12-20 Thread Ankit Singhal (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ankit Singhal updated HBASE-21020:
--
Attachment: HBASE-21020.HBASE-20952.005.patch

> Determine WAL API changes for replication
> -
>
> Key: HBASE-21020
> URL: https://issues.apache.org/jira/browse/HBASE-21020
> Project: HBase
>  Issue Type: Sub-task
>  Components: wal
>Reporter: Josh Elser
>Assignee: Ankit Singhal
>Priority: Major
> Fix For: HBASE-20952
>
> Attachments: HBASE-21020.HBASE-20952.001.patch, 
> HBASE-21020.HBASE-20952.002.patch, HBASE-21020.HBASE-20952.003.patch, 
> HBASE-21020.HBASE-20952.004.patch, HBASE-21020.HBASE-20952.005.patch
>
>
> Spin-off of HBASE-20952.
> Ankit has started working on what he thinks a WAL API specifically for 
> Replication should look like. In his own words:
> {quote}
> At a high level, it looks,
>  * Need to abstract WAL name under WalInfo instead of Paths
>  * Abstract the WalEntryStream for FileSystem and Streaming system.
>  * Build WalStorage APIs to abstract operation on Wal.
>  * Provide the implementation of all above through corresponding WalProvider
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HBASE-21020) Determine WAL API changes for replication

2018-12-19 Thread Ankit Singhal (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ankit Singhal updated HBASE-21020:
--
Attachment: HBASE-21020.HBASE-20952.004.patch

> Determine WAL API changes for replication
> -
>
> Key: HBASE-21020
> URL: https://issues.apache.org/jira/browse/HBASE-21020
> Project: HBase
>  Issue Type: Sub-task
>  Components: wal
>Reporter: Josh Elser
>Assignee: Ankit Singhal
>Priority: Major
> Fix For: HBASE-20952
>
> Attachments: HBASE-21020.HBASE-20952.001.patch, 
> HBASE-21020.HBASE-20952.002.patch, HBASE-21020.HBASE-20952.003.patch, 
> HBASE-21020.HBASE-20952.004.patch
>
>
> Spin-off of HBASE-20952.
> Ankit has started working on what he thinks a WAL API specifically for 
> Replication should look like. In his own words:
> {quote}
> At a high level, it looks,
>  * Need to abstract WAL name under WalInfo instead of Paths
>  * Abstract the WalEntryStream for FileSystem and Streaming system.
>  * Build WalStorage APIs to abstract operation on Wal.
>  * Provide the implementation of all above through corresponding WalProvider
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HBASE-21020) Determine WAL API changes for replication

2018-12-18 Thread Ankit Singhal (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ankit Singhal updated HBASE-21020:
--
Attachment: HBASE-21020.HBASE-20952.003.patch

> Determine WAL API changes for replication
> -
>
> Key: HBASE-21020
> URL: https://issues.apache.org/jira/browse/HBASE-21020
> Project: HBase
>  Issue Type: Sub-task
>  Components: wal
>Reporter: Josh Elser
>Assignee: Ankit Singhal
>Priority: Major
> Fix For: HBASE-20952
>
> Attachments: HBASE-21020.HBASE-20952.001.patch, 
> HBASE-21020.HBASE-20952.002.patch, HBASE-21020.HBASE-20952.003.patch
>
>
> Spin-off of HBASE-20952.
> Ankit has started working on what he thinks a WAL API specifically for 
> Replication should look like. In his own words:
> {quote}
> At a high level, it looks,
>  * Need to abstract WAL name under WalInfo instead of Paths
>  * Abstract the WalEntryStream for FileSystem and Streaming system.
>  * Build WalStorage APIs to abstract operation on Wal.
>  * Provide the implementation of all above through corresponding WalProvider
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HBASE-21020) Determine WAL API changes for replication

2018-12-18 Thread Ankit Singhal (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ankit Singhal updated HBASE-21020:
--
Attachment: (was: HBASE-21246.master.003.patch)

> Determine WAL API changes for replication
> -
>
> Key: HBASE-21020
> URL: https://issues.apache.org/jira/browse/HBASE-21020
> Project: HBase
>  Issue Type: Sub-task
>  Components: wal
>Reporter: Josh Elser
>Assignee: Ankit Singhal
>Priority: Major
> Fix For: HBASE-20952
>
> Attachments: HBASE-21020.HBASE-20952.001.patch, 
> HBASE-21020.HBASE-20952.002.patch, HBASE-21020.HBASE-20952.003.patch
>
>
> Spin-off of HBASE-20952.
> Ankit has started working on what he thinks a WAL API specifically for 
> Replication should look like. In his own words:
> {quote}
> At a high level, it looks,
>  * Need to abstract WAL name under WalInfo instead of Paths
>  * Abstract the WalEntryStream for FileSystem and Streaming system.
>  * Build WalStorage APIs to abstract operation on Wal.
>  * Provide the implementation of all above through corresponding WalProvider
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HBASE-21020) Determine WAL API changes for replication

2018-12-18 Thread Ankit Singhal (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ankit Singhal updated HBASE-21020:
--
Attachment: HBASE-21246.master.003.patch

> Determine WAL API changes for replication
> -
>
> Key: HBASE-21020
> URL: https://issues.apache.org/jira/browse/HBASE-21020
> Project: HBase
>  Issue Type: Sub-task
>  Components: wal
>Reporter: Josh Elser
>Assignee: Ankit Singhal
>Priority: Major
> Fix For: HBASE-20952
>
> Attachments: HBASE-21020.HBASE-20952.001.patch, 
> HBASE-21020.HBASE-20952.002.patch, HBASE-21246.master.003.patch
>
>
> Spin-off of HBASE-20952.
> Ankit has started working on what he thinks a WAL API specifically for 
> Replication should look like. In his own words:
> {quote}
> At a high level, it looks,
>  * Need to abstract WAL name under WalInfo instead of Paths
>  * Abstract the WalEntryStream for FileSystem and Streaming system.
>  * Build WalStorage APIs to abstract operation on Wal.
>  * Provide the implementation of all above through corresponding WalProvider
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HBASE-21020) Determine WAL API changes for replication

2018-12-13 Thread Ankit Singhal (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ankit Singhal updated HBASE-21020:
--
Attachment: HBASE-21020.HBASE-20952.002.patch

> Determine WAL API changes for replication
> -
>
> Key: HBASE-21020
> URL: https://issues.apache.org/jira/browse/HBASE-21020
> Project: HBase
>  Issue Type: Sub-task
>  Components: wal
>Reporter: Josh Elser
>Assignee: Ankit Singhal
>Priority: Major
> Fix For: HBASE-20952
>
> Attachments: HBASE-21020.HBASE-20952.001.patch, 
> HBASE-21020.HBASE-20952.002.patch
>
>
> Spin-off of HBASE-20952.
> Ankit has started working on what he thinks a WAL API specifically for 
> Replication should look like. In his own words:
> {quote}
> At a high level, it looks,
>  * Need to abstract WAL name under WalInfo instead of Paths
>  * Abstract the WalEntryStream for FileSystem and Streaming system.
>  * Build WalStorage APIs to abstract operation on Wal.
>  * Provide the implementation of all above through corresponding WalProvider
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HBASE-21020) Determine WAL API changes for replication

2018-12-13 Thread Ankit Singhal (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ankit Singhal updated HBASE-21020:
--
Fix Version/s: HBASE-20952
   Status: Patch Available  (was: Open)

> Determine WAL API changes for replication
> -
>
> Key: HBASE-21020
> URL: https://issues.apache.org/jira/browse/HBASE-21020
> Project: HBase
>  Issue Type: Sub-task
>  Components: wal
>Reporter: Josh Elser
>Assignee: Ankit Singhal
>Priority: Major
> Fix For: HBASE-20952
>
> Attachments: HBASE-21020.HBASE-20952.001.patch
>
>
> Spin-off of HBASE-20952.
> Ankit has started working on what he thinks a WAL API specifically for 
> Replication should look like. In his own words:
> {quote}
> At a high level, it looks,
>  * Need to abstract WAL name under WalInfo instead of Paths
>  * Abstract the WalEntryStream for FileSystem and Streaming system.
>  * Build WalStorage APIs to abstract operation on Wal.
>  * Provide the implementation of all above through corresponding WalProvider
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HBASE-21020) Determine WAL API changes for replication

2018-12-12 Thread Ankit Singhal (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HBASE-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ankit Singhal updated HBASE-21020:
--
Attachment: HBASE-21020.HBASE-20952.001.patch

> Determine WAL API changes for replication
> -
>
> Key: HBASE-21020
> URL: https://issues.apache.org/jira/browse/HBASE-21020
> Project: HBase
>  Issue Type: Sub-task
>  Components: wal
>Reporter: Josh Elser
>Assignee: Ankit Singhal
>Priority: Major
> Attachments: HBASE-21020.HBASE-20952.001.patch
>
>
> Spin-off of HBASE-20952.
> Ankit has started working on what he thinks a WAL API specifically for 
> Replication should look like. In his own words:
> {quote}
> At a high level, it looks,
>  * Need to abstract WAL name under WalInfo instead of Paths
>  * Abstract the WalEntryStream for FileSystem and Streaming system.
>  * Build WalStorage APIs to abstract operation on Wal.
>  * Provide the implementation of all above through corresponding WalProvider
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)