Merge "[Trivialfix]Fix typos in trove"
This commit is contained in:
commit
af4c0a5ae6
@ -4,5 +4,5 @@ fixes:
|
||||
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
|
||||
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.
|
||||
|
@ -18,7 +18,7 @@ from trove.common.context import TroveContext
|
||||
|
||||
|
||||
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.
|
||||
"""
|
||||
|
||||
|
@ -556,7 +556,7 @@ tombstone_failure_threshold: 100000
|
||||
# Increase if your rows are large, or if you have a very large
|
||||
# number of rows per partition. The competing goals are these:
|
||||
# 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
|
||||
# 2) but, Cassandra will keep the collation index in memory for hot
|
||||
# rows (as part of the key cache), so a larger granularity means
|
||||
|
Loading…
x
Reference in New Issue
Block a user