Bug 1195646 - Add a new API to get first Changelog entry in latest HTIME file
Summary: Add a new API to get first Changelog entry in latest HTIME file
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Saravanakumar
QA Contact: Saravanakumar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-24 08:55 UTC by Saravanakumar
Modified: 2015-10-30 08:38 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-10-30 08:38:10 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Saravanakumar 2015-02-24 08:55:32 UTC 
Description of problem:

To add a  new API gf_get_first_changelog added in libgfchagelog libraryto get the first changelog file entry present in the latest HTIME file.

Provide an example on how to make use of this API.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Should be able to get the first CHANGELOG file entry using the provided buffer to the API. 

Expected results:


Additional info:
This API can be make use by Geo-replication to get the first entry in 
latest htime file.
Comment 1 Anand Avati 2015-02-24 09:25:10 UTC 
REVIEW: http://review.gluster.org/9730 (geo-rep: A new API to get first changelog entry in the htime file) posted (#3) for review on master by Saravanakumar Arumugam (sarumuga)
Comment 2 Anand Avati 2015-04-22 05:55:40 UTC 
REVIEW: http://review.gluster.org/9730 (geo-rep: A new API to get first changelog entry in the htime file [WIP]) posted (#4) for review on master by Saravanakumar Arumugam (sarumuga)
Note You need to log in before you can comment on or make changes to this bug.