Make Statement.setPagingSize method public

[virtan]

Make Statement.setPagingSize method public

Motivation:

In some cases we may need to change paging size to reduce chances of read timeouts

Modifications:

The method setPagingSize() existed but wasn't public so was inaccessible for clients

Result:

With this change it would become public and let a client to set custom paging sizes on per statement basis

[glbrntt]

Can we use Int instead here? It should be preferred for public APIs.

[yifan-c]

What is the rationale of using Int, besides the preference for public API?
Cassandra's native protocol accepts 32-bits int. From this perspective, Int32 reflects the API constraint precisely, meanwhile Int can be 64-bits depending on the platform, potentially causing overflow theoretically. In reality, no one should set the page size this large.

[virtan]

There is a variant of execute() method which also expects pageSize in Int32. It is public already, so changing it may introduce some backward compatibility issues.

[glbrntt]

There is a variant of execute() method which also expects pageSize in Int32. It is public already, so changing it may introduce some backward compatibility issues.

That one should ideally be Int too, we can separately deprecate that variant of execute and add one using Int.

I'd much rather we course correct and add appropriate APIs rather than being consistent with past mistakes.