Unlike Elasticsearch, can the number of shards be changed in Elassandra as in Cassandra?

[fdsmax]

Sorry for a silly a question. I'm aware, the number_of_shards is a fixed value in Elasticsearch as this can not be changed after creating the index. Whereas the new nodes (shard or partition node) can be added to the Cassandra ring. From the notes, I guess the Elassandra uses the Cassandra config for the keyspace storage layer and it's partitioner type etc. Just to confirm, does Elassandra inherits the number of shards (config) from Cassandra or Elasticsearch? In other words, can the number of shards be changed for Elassandra index later stage after creating it?

[fdsmax]

@vroyer Ignore my question above. I found the answer for my query about changing the Shards, from your documentation at: https://media.readthedocs.org/pdf/elassandra/latest/elassandra.pdf

Excerpt from your document that helped me: "Unlike Elasticsearch, sharding depends on the number of nodes in the datacenter, and number of replica is defined by your keyspace Replication Factor . Elasticsearch numberOfShards is just an information about number of nodes.
• When adding a new elasticassandra node, the cassandra boostrap process gets some token ranges from the existing ring and pull the corresponding data. Pulled data are automatically indexed and each node update its routing table to distribute search requests according to the ring topology." .....

Thanks,
Diwakar