GitHub user snoopdave opened a pull request:
https://github.com/apache/usergrid/pull/508
don
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/snoopdave/usergrid release-2.1.1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/usergrid/pull/508.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 #508
----
commit 8c725f19aa30a1cca5b71017c8a43586b6e4d544
Author: Michael Russo <[email protected]>
Date: 2016-03-14T23:07:19Z
Initial work to iterate over the shards with more context so we don't fetch
all rows (shards) at the same time always.
commit 92fae0df4d99e6e5d14811f6ba3680487a0b71b9
Author: Michael Russo <[email protected]>
Date: 2016-03-15T00:27:16Z
Set verbose logging to trace.
commit 10e2be7b405e1031abf74082efa8dce2ca9cb1fc
Author: Mike Dunker <[email protected]>
Date: 2016-03-15T19:30:25Z
USERGRID-1266: check permissions at REST layer to avoid incorrect response
codes
also block user token exchange via GET
/org/app/users/{user}/token?access_token={usertoken}
commit 4bbebc5fd759efe59bae612c9f47e36589750982
Author: Michael Russo <[email protected]>
Date: 2016-03-16T04:59:21Z
Clean up the logging, ensure the order of shard iterator within
MultiRowColumnIterator is correct. Restore NodeShardCache logic.
commit b112488db1ef01ee8417e35e48e428c40d0aa206
Author: Michael Russo <[email protected]>
Date: 2016-03-17T00:25:22Z
Make the shard consistency tests a little smarter. Update shard compaction
to be a safer background process by updating the edge writes to be atomic, and
the deletes delayed (ensures data will always be available for seeking and we
filter any dupes).
commit 4e407ff690f220ee04c535a5ce91ca5a3a07ad1d
Author: Michael Russo <[email protected]>
Date: 2016-03-18T05:12:51Z
Add 'smart' shard seeking into the multi row column iterator. This
leverages a stored 'end' edge marked on a shard at the end of compacting and
balancing a shard's (row's) edges (columns).
commit 58ae197ea581f271de644760531a9cd45287c7c9
Author: Michael Russo <[email protected]>
Date: 2016-03-18T21:31:30Z
Throttle the compactions and auditing such that the 'type' can only be
compacted one at a time (source or target node shard(s))
commit bec5093978175c87b7d76f66c8a503f062275ead
Author: Michael Russo <[email protected]>
Date: 2016-03-21T00:49:10Z
Reset original multi-row column iterator and use a new class for the smart
iterating over edge shards. Change to system time for 'last write wins' in
cassandra instead of a shard's 'createdTime'.
commit bd7767233193ca8c9cde164dee3b1475aefcc440
Author: Michael Russo <[email protected]>
Date: 2016-03-21T01:44:41Z
Clean up some comments and unused code.
commit 11d8a0edebd63b05314c711b457cc03e4a477599
Author: Michael Russo <[email protected]>
Date: 2016-03-21T02:18:44Z
Add a timeout to one the graph shard tests so it can't run forever in the
event that it is failing.
commit 1e2b082704b1fa1ff3ae4fbdf5afa69902f4aa26
Author: Michael Russo <[email protected]>
Date: 2016-03-21T05:52:31Z
Fix info log statement to be trace.
commit 4c41f1bdc878190076deb875c7c5fd202487a0d0
Author: Michael Russo <[email protected]>
Date: 2016-03-21T05:56:10Z
Remove unused import.
commit 4d828e1cdba69430b06337988e91490eaf0cfd1b
Author: Michael Russo <[email protected]>
Date: 2016-03-21T18:12:34Z
Add additional filter for index processing to ensure things do not get
ack'd that should not get ack'd.
commit aef26b9bc0d3af7131aec16b49fe27f4af081e41
Author: Michael Russo <[email protected]>
Date: 2016-03-21T18:40:21Z
Update variable reference for async event creation time.
commit 903fd1864465819ea055dab8d41e6d336f582491
Author: Michael Russo <[email protected]>
Date: 2016-03-21T19:51:49Z
Upgrade to ES 1.7.3 Java client and remove incorrect filter on async events.
commit 85cd12d106bde2398c1132ef2d4a439166bb2035
Author: Michael Russo <[email protected]>
Date: 2016-03-21T20:00:29Z
Fix bad comment.
commit 9771968408658e8ce4c14db305bc10fc173d65d8
Author: Michael Russo <[email protected]>
Date: 2016-03-23T01:16:44Z
Fix issue where new shards were not picked up after new shards are
allocated.
commit 317b1827491bd481eba6839076c702f142178b41
Author: Michael Russo <[email protected]>
Date: 2016-03-23T01:32:37Z
Increase test readers to 2.
commit 39351f1eb59008348dc2b1812b2cf5159f693721
Author: Michael Russo <[email protected]>
Date: 2016-03-23T03:14:22Z
Update the cache invalidation to be specific for the key and not invalidate
the whole cache.
commit e64fa3503069f41b66e3942a946b14d7222e1525
Author: Michael Russo <[email protected]>
Date: 2016-03-23T17:32:30Z
Merge commit 'refs/pull/493/head' of github.com:apache/usergrid into
release-2.1.1
commit b9e808841d61688e9b752649130119f0afb1e079
Author: Michael Russo <[email protected]>
Date: 2016-03-23T20:00:07Z
Disable reading from shard cache when obtaining read shard groups so it's
always accurate.
commit 879cdeffcbd7e8cdab8c25fa61e606b6ea6a1bbe
Author: Michael Russo <[email protected]>
Date: 2016-03-23T21:17:28Z
Fix legacy column parser for edge shards.
commit 56e03718a911a6a1215fa75522b54ad694c4b566
Author: George Reyes <[email protected]>
Date: 2016-03-03T16:20:30Z
Adding in beginning test.
commit 58e6cf38660350b16f3d443dfe781bc9f1c90903
Author: George Reyes <[email protected]>
Date: 2016-03-07T18:40:27Z
Added a method to properly set the owner ( at least the email ) to the
schema map in elastic search
Removed traces of creating a new column family. Map manager is the way to
go.
Added the get endpoint to the service resource that will allow us to do
gets.
Added a way for the endpoint to read the JSON response and did the specific
call out so that we could work around having to make a service ( Which is bad
code )
Returned an object with a terrible name to debug the response that gets
returned.
Added AbstractCollectionService method that allows us to get the workaround
to a normal call in order to get around path permission checking.
AbstractService has the workaround which is what needs to be done if you
want to avoid using a schema.
Added a new service action for the work around.
commit 99c75ccd6ca16f93e3be934e5f1c5455d6e375c5
Author: George Reyes <[email protected]>
Date: 2016-03-09T20:18:36Z
Cherry picking 2 more commits with the working selective indexing but
improperly
commit aa7f776edae7f9a2cb4c1577b6c86e1c028f082a
Author: George Reyes <[email protected]>
Date: 2016-03-11T23:19:52Z
Another cherry pick with another issue with collection resource it and
nothing else.
commit 3c98c2ddefc799924d4069b6010eac4e561a69b2
Author: George Reyes <[email protected]>
Date: 2016-03-12T00:25:25Z
Cleaned up the test
commit a2ec1dfaf8ea76e7e660f7103ebfabeded57cff0
Author: George Reyes <[email protected]>
Date: 2016-03-14T19:28:35Z
no message
commit f0480b4881a097e50ad2153e735268834b40dbb9
Author: George Reyes <[email protected]>
Date: 2016-03-16T18:38:10Z
no message
commit c0b96a56729e8f1bf10a6c883756dbedb08a4baa
Author: George Reyes <[email protected]>
Date: 2016-03-16T22:21:04Z
Ignored test that isn't currently supported due to needing a new endpoint.
Added logic that will index entire arrays by only specifying the top level
identifier.
----
---
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.
---
