AWS GO SDK's CLOUDWATCH MODULE LIMIT NOT RESPECTED IN cloudwatchlogs.StartQueryInput struct

[anees-tricon]

Confirm by changing [ ] to [x] below to ensure that it's a bug:

• I've gone though Developer Guide and API reference
• I've checked AWS Forums and StackOverflow for answers
• I've searched for previous similar issues and didn't find any solution

Describe the bug
Query Limit value mentioned in cloudwatchlogs.StartQueryInput Struct is not being respected in StartQuery method.
Example:-

	queryInputStruct := &cloudwatchlogs.StartQueryInput{
		LogGroupName: aws.String(programInput.LogGroupName),
		StartTime:    aws.Int64(queryInputData[0]),
		EndTime:      aws.Int64(queryInputData[1]),
		QueryString:  aws.String(programInput.LogQuery),
                Limit: aws.Int64(10000)
	}

This always retrieves only 1000 records irrespective of the mentioned limit. But If we mention the limit in query itself then it works.

Thanks in advance!!

Version of AWS SDK for Go?
Example: v1.29.22

• get SDK version by printing the output of aws.SDKVersion in your code after importing "github.com/aws/aws-sdk-go/aws"
  latest stable one

Version of Go (go version)?
1.14.4

To Reproduce (observed behavior)
Steps to reproduce the behavior (please share code or minimal repo)

Expected behavior
A clear and concise description of what you expected to happen.

Additional context
Add any other context about the problem here.

[NGL321]

Hi @anees-tricon,

We apologize for the delays on a response. Thank you for reporting this bug! It seems to be an issue with the service API for Cloudwatch and therefore affects all the SDKs. We will track it here in this repo. You can watch this issue for updates as a fix gets evaluated and implemented.

😸 😷

[RCHowell]

A ticket has been opened to the service team

[jmklix]

P47842982

[jmklix]

This has been added to an internal queue. Closing this issue

[github-actions]

This issue is now closed.

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.