Build Update for apache/geode-examples
-
Build: #522
Status: Passed
Duration: 23 mins and 38 secs
Commit: 12a3c52 (support/1.14)
Author: Owen Nichols
Message: Bumping copyright year to 2021
View the changeset: https://github.com/apache/geode-examples/commit/12
Build Update for apache/geode-examples
-
Build: #523
Status: Errored
Duration: 1 min and 9 secs
Commit: d8b16a6 (develop)
Author: Owen Nichols
Message: pair develop examples with 1.15.0 now that support/1.14 has been
created
View the changeset:
https://githu
Build Update for apache/geode-native
-
Build: #3028
Status: Passed
Duration: 1 hr, 16 mins, and 33 secs
Commit: ba8fd9b (rel/v1.12.1.RC3)
Author: Owen Nichols
Message: Bumping copyright year to 2021
View the changeset:
https://github.com/apache/geode-native/c
Build Update for apache/geode-native
-
Build: #3026
Status: Passed
Duration: 1 hr, 17 mins, and 5 secs
Commit: 21fcdb8 (rel/v1.12.1.RC2)
Author: Owen Nichols
Message: Bumping copyright year to 2021
View the changeset:
https://github.com/apache/geode-native/co
Build Update for apache/geode-native
-
Build: #3024
Status: Passed
Duration: 1 hr, 15 mins, and 59 secs
Commit: 21fcdb8 (rel/v1.12.1.RC1)
Author: Owen Nichols
Message: Bumping copyright year to 2021
View the changeset:
https://github.com/apache/geode-native/c
Hello Geode Dev Community,
One year ago this month, Geode adopted a plan to maintain N-2 support branches
[1] and support/1.12 was created. Over 140 fixes have now been backported to
support/1.12 since 1.12.0 was released, so I’d like to propose a maintenance
release!
My apologies, RC1 and RC
Build Update for apache/geode-examples
-
Build: #521
Status: Errored
Duration: 1 min and 11 secs
Commit: f27cc8d (rel/v1.12.1.RC3)
Author: Owen Nichols
Message: Revert "temporarily point to staging repo for CI purposes"
View the changeset:
https://github.com/
Build Update for apache/geode-examples
-
Build: #519
Status: Canceled
Duration: ?
Commit: 552a4b6 (support/1.12)
Author: Owen Nichols
Message: temporarily point to staging repo for CI purposes
View the changeset:
https://github.com/apache/geode-examples/compa
Build Update for apache/geode-examples
-
Build: #517
Status: Passed
Duration: 25 mins and 18 secs
Commit: c4cf1c4 (support/1.12)
Author: Owen Nichols
Message: Bumping version to 1.12.1
View the changeset:
https://github.com/apache/geode-examples/compare/2737d
Build Update for apache/geode-examples
-
Build: #514
Status: Passed
Duration: 25 mins and 57 secs
Commit: d235195 (support/1.12)
Author: Owen Nichols
Message: Bumping version to 1.12.1
View the changeset:
https://github.com/apache/geode-examples/compare/10fa6
Build Update for apache/geode-examples
-
Build: #518
Status: Errored
Duration: 1 min and 8 secs
Commit: b88adb4 (rel/v1.12.1.RC2)
Author: Owen Nichols
Message: Revert "temporarily point to staging repo for CI purposes"
View the changeset:
https://github.com/a
Build Update for apache/geode-examples
-
Build: #516
Status: Canceled
Duration: ?
Commit: 2737dc2 (support/1.12)
Author: Owen Nichols
Message: temporarily point to staging repo for CI purposes
View the changeset:
https://github.com/apache/geode-examples/compa
Build Update for apache/geode-examples
-
Build: #515
Status: Errored
Duration: 1 min and 9 secs
Commit: f097cb0 (rel/v1.12.1.RC1)
Author: Owen Nichols
Message: Bumping version to 1.12.1
View the changeset:
https://github.com/apache/geode-examples/compare/rel/
Hi Alberto,
I haven't checked the PR yet, just read through the email. The first thought
that comes to mind is when someone does a != query. The index still has to
supply the correct answer to the query (all entries with null or undefined
values possibly)
I'll try to think of other cases whe
Build Update for apache/geode-examples
-
Build: #513
Status: Canceled
Duration: ?
Commit: 10fa613 (support/1.12)
Author: Owen Nichols
Message: temporarily point to staging repo for CI purposes
View the changeset:
https://github.com/apache/geode-examples/compa
Hello, may I please have access to the Geode Concourse?
My GitHub username is pdxcodemonkey
Thanks,
Blake
Hi,
We have observed that creating an index on a Map field causes the creation of
an index entry for every entry created in the region containing the Map, no
matter if the Map field contained the key used in the index.
Nevertheless, we would expect that only entries whose Map field contain the k
17 matches
Mail list logo