Get-CohesityObject limited to 100 (random) objects

[regloff72]

🐛 Bug Report

Get-CohesityObject seems to be limited to 100 random objects. Is this by design? I am guessing not, but thought I would ask. The help page did not mention an object limit.

We probably have well over 2,000 hosts under the registered sources on one of our clusters and this will only return 100 maximum.

For an example of what I am seeing here.. (In this case for me, I could very well use 'Get-CohesityVM' to accomplish my specific goal) but thought it might prove useful to mention this. :)

Same cluster / Same Session for these two outputs:

PS C:\WINDOWS\system32> $test = (Get-CohesityObject -SearchString *)
PS C:\WINDOWS\system32> $test.Length
100

PS C:\WINDOWS\system32> $test2 = (Get-CohesityVMwareVM)
PS C:\WINDOWS\system32> $test2.Length
3785

To Reproduce

(Write your steps here:)

1. Execute Get-CohesityObject -SearchString * - on a cluster where more than 100 objects exist
2. Tested length at different times/connections to cluster. Length never exceeds 100.
3. Conversely, Get-CohesityVMwareVM will return a more expected number on our cluster (3785 hosts)

Expected behavior

Expectation that "Get-CohesityObject -SearchString *" would retrieve all objects on the cluster, similar to how Get-CohesityVMwareVM returns all VM objects on the cluster.

(Write what you thought would happen.)

Actual Behavior

When provding the least restrictive search string "*" - Get-CohesityObject will only return 100 random objects (specific object vary)

(Write what happened. Add screenshots, if applicable.)

Tested cmdlet with various patterns. Any known pattern that exceeds 100 hosts will be truncated at 100. Queries of less than 100 return accurate results.

PS C:\WINDOWS\system32> $test = (Get-CohesityObject -SearchString *)
PS C:\WINDOWS\system32> $test.Length
100

PS C:\WINDOWS\system32> $test393 = (Get-CohesityObject -SearchString 393)
PS C:\WINDOWS\system32> $test393.Length
76

PS C:\WINDOWS\system32>