Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport #1233 to 2.0 #1253

Closed
wants to merge 1 commit into from
Closed

Backport #1233 to 2.0 #1253

wants to merge 1 commit into from

Conversation

kuenishi
Copy link
Contributor

Merge CV's list-objects prefix optimization + Add key length limit [JIRA: RCS-275 (#1233)]

Conflicts:
src/riak_cs_s3_response.erl
src/riak_cs_wm_object.erl
src/riak_cs_wm_object_upload_part.erl

Merge CV's list-objects prefix optimization + Add key length limit [JIRA: RCS-275]

Reviewed-by: shino

Conflicts:
	src/riak_cs_s3_response.erl
	src/riak_cs_wm_object.erl
	src/riak_cs_wm_object_upload_part.erl
@kuenishi kuenishi added this to the 2.0.2 milestone Sep 18, 2015
@shino
Copy link
Contributor

shino commented Sep 24, 2015

  • It seems that the first line of commit message is somewhat misleading.
  • xref and dialyzer are failing

status_code(invalid_access_key_id) -> 403;
status_code(invalid_email_address) -> 400;
status_code(access_denied) -> 403;
status_code(copy_source_access_denied) -> 403;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This error atom is not used anywhere else?

@kuenishi
Copy link
Contributor Author

kuenishi commented Oct 1, 2015

After several review and thoughts I think we had better not backport to 2.0. It is easier to resolve conflicting key validation when merging back to 2.1.

@kuenishi kuenishi closed this Oct 1, 2015
@kuenishi kuenishi deleted the feature/list-keys-optimization branch October 1, 2015 01:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants