diff options
| author | Poornima G <pgurusid@redhat.com> | 2017-11-18 15:19:13 +0530 |
|---|---|---|
| committer | Amar Tumballi <amarts@redhat.com> | 2017-12-05 14:21:01 +0000 |
| commit | dc1258bfe46d30059119a3294285a114ec2bcd36 (patch) | |
| tree | 4ff3cb254b5246e27b1eda32312e4ddeec897900 /libglusterfs/src/defaults-tmpl.c | |
| parent | 8a0b115b20cfa2dd3c5a9e22a8244c9c2f03e17b (diff) | |
libglusterfs: Add put fop
Problem: It had been a longtime request to implement put fop
in gluster. put fop in gluster may not have the exact sementics
of HTTP PUT, but can be easily extended to do so. The subsequent
patches, will contain more semantics on the put fop and its
guarentees.
Why compound fop framework is not used for put?
Compound fop framework currently doesn't allow compounding of
entry fop and inode fops, i.e. fops on multiple inodes cannot be
combined in compound fop.
Updates #353
Change-Id: Idb7891b3e056d46d570bb7e31bad1b6a28656ada
Signed-off-by: Poornima G <pgurusid@redhat.com>
Diffstat (limited to 'libglusterfs/src/defaults-tmpl.c')
| -rw-r--r-- | libglusterfs/src/defaults-tmpl.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/libglusterfs/src/defaults-tmpl.c b/libglusterfs/src/defaults-tmpl.c index d311972f0c0..21b99d9566c 100644 --- a/libglusterfs/src/defaults-tmpl.c +++ b/libglusterfs/src/defaults-tmpl.c @@ -81,6 +81,7 @@ struct xlator_fops _default_fops = { .getspec = default_getspec, .getactivelk = default_getactivelk, .setactivelk = default_setactivelk, + .put = default_put, }; struct xlator_fops *default_fops = &_default_fops; |