openstack/trove
Code Issues Proposed changes

Merge "[Trivialfix]Fix typos in trove"

Browse Source
This commit is contained in:
Zuul 2017-11-03 19:01:55 +00:00 committed by Gerrit Code Review
commit af4c0a5ae6
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
releasenotes/notes/fix-cluster-type-error-71cd846897dfd32e.yaml
View File

@ -4,5 +4,5 @@ fixes:
while setting the nics on a create call. When we called cast to set() while setting the nics on a create call. When we called cast to set()
the object was a list of lists. The set method can not has a list so the object was a list of lists. The set method can not has a list so
this was causesing a unhashable error. The change is to make the this was causesing a unhashable error. The change is to make the
instance_nics a list of strings (what we originaly expected) to instance_nics a list of strings (what we originally expected) to
resolve this issue. Bug 1570602. resolve this issue. Bug 1570602.

2
trove/common/rpc/serializer.py
View File

@ -18,7 +18,7 @@ from trove.common.context import TroveContext
class TroveSerializer(messaging.Serializer): class TroveSerializer(messaging.Serializer):
"""The Trove serializer class that handles class inheritence and base """The Trove serializer class that handles class inheritance and base
serializers. serializers.
""" """

2
trove/templates/cassandra/config.template
View File

@ -556,7 +556,7 @@ tombstone_failure_threshold: 100000
# Increase if your rows are large, or if you have a very large # Increase if your rows are large, or if you have a very large
# number of rows per partition. The competing goals are these: # number of rows per partition. The competing goals are these:
# 1) a smaller granularity means more index entries are generated # 1) a smaller granularity means more index entries are generated
# and looking up rows withing the partition by collation column # and looking up rows within the partition by collation column
# is faster # is faster
# 2) but, Cassandra will keep the collation index in memory for hot # 2) but, Cassandra will keep the collation index in memory for hot
# rows (as part of the key cache), so a larger granularity means # rows (as part of the key cache), so a larger granularity means