GitHub user GERey opened a pull request:
https://github.com/apache/usergrid/pull/466
Usergrid 1047
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/usergrid USERGRID-1047
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/usergrid/pull/466.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #466
----
commit dae825429656871f97bba71b79a764e9c8976121
Author: George Reyes <[email protected]>
Date: 2016-01-13T20:18:53Z
Added test that verify that doing a get on an asset will now return on 404
and added AmazonException throwing for reading.
commit ee8c7c4d023db8cc3b5c7dfb274492c2475de5c5
Author: George Reyes <[email protected]>
Date: 2016-01-14T19:19:05Z
Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/usergrid
into USERGRID-1047
# Via Dave Johnson (1) and George Reyes (1)
* 'master' of https://git-wip-us.apache.org/repos/asf/usergrid:
Added apache header to testing text. Fun fact time: The apache header
adds 803 bytes unto every file. For the 251 files of apache rat checked files
we use 201 KB on headers alone!
Added some comments and deleting found commented out code.
Created a test that correctly emulates what occurs when running curl
asset call.
Added additional test file and test case to verify the issue in
USERGRID-144. Also, added fix to file not getting rid of text metadata and
being properly replaced by image asset.
commit d97f6e3c5d219ed8ca69be492d5d0dc9c45fd3a4
Author: George Reyes <[email protected]>
Date: 2016-01-14T20:12:42Z
Fixed assets tests and fixed oversight of not updating entity metadata for
AWS binary assets.
Also changed tests so they will run with properties set the way its done
occasionally.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
