When using the hca dss post-search command it lists --search-after option which cannot be used from the CLI. You must have the "next" field from the header in order to use that option, and there isn't a way to get the "next" field out of the header using the CLI.
There is also a lot of extra documentation included that is not pertinent to the CLI. All the documentation around how to use the "next" field is not applicable to the way that the CLI works at this time.
Reproduction
hca dss post-search --es-query "{}" --replica=aws
Note that there isn't any "next" value included in the output. his is true when using the --output-format raw option.
hca dss post-search --help
will display lots of information about how to use the "next" value for pagination.
kozbo
commented
6 years ago
Problem:
When using the
hca dss post-searchcommand it lists--search-afteroption which cannot be used from the CLI. You must have the "next" field from the header in order to use that option, and there isn't a way to get the "next" field out of the header using the CLI.There is also a lot of extra documentation included that is not pertinent to the CLI. All the documentation around how to use the "next" field is not applicable to the way that the CLI works at this time.
Reproduction
hca dss post-search --es-query "{}" --replica=awsNote that there isn't any "next" value included in the output. his is true when using the--output-format rawoption.hca dss post-search --helpwill display lots of information about how to use the "next" value for pagination.