Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
cta
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Harbor Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
dCache
cta
Commits
20e496a2
Commit
20e496a2
authored
3 years ago
by
Tigran Mkrtchyan
Browse files
Options
Downloads
Patches
Plain Diff
cta-dcache: drop 'transport' field from DeleteRequest
parent
6aae4efa
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
cta-dcache/grpc-proto/protobuf/cta_rpc.proto
+2
-3
2 additions, 3 deletions
cta-dcache/grpc-proto/protobuf/cta_rpc.proto
with
2 additions
and
3 deletions
cta-dcache/grpc-proto/protobuf/cta_rpc.proto
+
2
−
3
View file @
20e496a2
...
...
@@ -65,9 +65,8 @@ message RetrieveRequest {
message
DeleteRequest
{
cta.common.Service
instance
=
1
;
// client instance ID
cta.eos.Client
cli
=
2
;
// requester information
cta.eos.Transport
transport
=
3
;
// IO, error and success endpoints
FileInfo
file
=
4
;
// files' metadata
uint64
archiveId
=
5
;
// tape system unique file ID
FileInfo
file
=
3
;
// files' metadata
uint64
archiveId
=
4
;
// tape system unique file ID
}
service
CtaRpc
{
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment