[
https://issues.apache.org/jira/browse/GEODE-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-2719:
---
Component/s: docs
> The total-max-memory region attribute does not appear to do anythi
Congratulations Ernie!
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: +1-631-835-4771
On Fri, Mar 24, 2017 at 7:22 PM, Nabarun Nag wrote:
> Congrats and welcome !!! :)
>
> On Fri, Mar 24, 2017 at 3:41 PM Bruce Schuchardt
> wrote:
>
> > Welcome to the group Ernie!
> >
> > Le
[
https://issues.apache.org/jira/browse/GEODE-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-2653:
---
Assignee: Galen O'Sullivan
> GMSJoinLeaveJUnitTest.testRemoveMember fails with Assert
Hi!
$ git diff --stat rel/v1.1.0..rel/v1.1.1.RC1
...
683 files changed, 1785472 insertions(+), 1437 deletions(-)
Is this amount of change really necessary for a patch release?
Thanks,
Roman.
On Sat, Mar 25, 2017 at 9:34 AM, Anthony Baker wrote:
> This is the first release candidate of the rele
[
https://issues.apache.org/jira/browse/GEODE-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943608#comment-15943608
]
Bruce Schuchardt commented on GEODE-2718:
-
The membership service will need to del
[
https://issues.apache.org/jira/browse/GEODE-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider resolved GEODE-2472.
-
Resolution: Fixed
Fix Version/s: 1.2.0
> Oplog.flush method doesn't verify that the
[
https://issues.apache.org/jira/browse/GEODE-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943655#comment-15943655
]
Hitesh Khamesra commented on GEODE-2658:
Hi Shrumit:
Geode java server can be con
Karen Smoler Miller created GEODE-2720:
--
Summary: Docs should have 2-digit release number, not 3-digit
Key: GEODE-2720
URL: https://issues.apache.org/jira/browse/GEODE-2720
Project: Geode
It looks like almost all of these changes are in geode-site/website
Le 3/27/2017 à 9:38 AM, Roman Shaposhnik a écrit :
Hi!
$ git diff --stat rel/v1.1.0..rel/v1.1.1.RC1
...
683 files changed, 1785472 insertions(+), 1437 deletions(-)
Is this amount of change really necessary for a patch release?
Welcome Ernie!
--Mark
On Mon, Mar 27, 2017 at 9:33 AM, Michael Stolz wrote:
> Congratulations Ernie!
>
> --
> Mike Stolz
> Principal Engineer, GemFire Product Manager
> Mobile: +1-631-835-4771
>
> On Fri, Mar 24, 2017 at 7:22 PM, Nabarun Nag wrote:
>
> > Congrats and welcome !!! :)
> >
> > On
Github user asfgit closed the pull request at:
https://github.com/apache/geode-native/pull/73
---
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
[
https://issues.apache.org/jira/browse/GEODE-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943720#comment-15943720
]
ASF subversion and git services commented on GEODE-2513:
Commit 27
[
https://issues.apache.org/jira/browse/GEODE-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943721#comment-15943721
]
ASF subversion and git services commented on GEODE-2513:
Commit 27
[
https://issues.apache.org/jira/browse/GEODE-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943719#comment-15943719
]
ASF subversion and git services commented on GEODE-2513:
Commit da
[
https://issues.apache.org/jira/browse/GEODE-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943722#comment-15943722
]
ASF GitHub Bot commented on GEODE-2513:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/GEODE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943739#comment-15943739
]
Kevin Duling commented on GEODE-2613:
-
Confirmed {{DATA:WRITE}} is in place for the RE
I was about to writing some JMH benchmarks for specific areas of Geode code
and place the benchmarks in src/jmh/java parallel to src/main/java and
src/tests/java in the appropriate geode module containing the code I want
to benchmark.
I see that we already have a "geode-benchmarks" module which se
The release/1.1.1 branch was made from master which shows several
documentation-related changes after the 1.1.0 release:
commit 7f0f4d5f92ea04ff48c5dae823848636c910e06b
Author: Karen Miller
Date: Thu Feb 16 15:37:16 2017 -0800
GEODE-2498 Revise published 1.1.0 manual, so it has
no ref
I believe it would be much better user experience if we just serialized
user's domain object without requiring the user to configure anything.
Currently, we require that the user specify that they want to use the
ReflectionBasedAutoSerializer and the pattern that matches the domain
objects.
Lookin
+1 I think we should make the default serialization mechanism to be PDX.
We should not concern ourselves with Java serialization at all anymore.
+1 pdx-read-serialization=true ... I think we should prefer PdxInstance
objects over customer POJOs. I think that customers would be ok to run
PdxIns
I generally don't see a problem with this from the *Spring* side, i.e. SDG
does not care as long as the "default" PdxSerializer (e.g.
ReflectionBasedAutoSerializer or whatever) is "overridable" before cache
initialization!
However, I definitely disagree with this...
*> I think that customers wou
On Mon, Mar 27, 2017 at 12:13 PM, Anthony Baker wrote:
> The release/1.1.1 branch was made from master which shows several
> documentation-related changes after the 1.1.0 release:
I understand that, but I think in this particular case a patch release
should be as close to 1.1.0 as possible.
If t
Most new customers just want Geode/ GemFire to work - easily - because most
projects don't require dealing with PDX. In fact, some explicitly tell me
that they don't want to know about PDX because it's a distraction for the
simple use-cases. This is, of course, with the caveat that unless they need
[
https://issues.apache.org/jira/browse/GEODE-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944033#comment-15944033
]
Kevin Duling commented on GEODE-1994:
-
In GEODE-2704, the custom StringUtil was droppe
[
https://issues.apache.org/jira/browse/GEODE-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944033#comment-15944033
]
Kevin Duling edited comment on GEODE-1994 at 3/27/17 8:58 PM:
--
[
https://issues.apache.org/jira/browse/GEODE-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-2632:
Assignee: Kirk Lund
> Integrated Security performance improvements
> --
[
https://issues.apache.org/jira/browse/GEODE-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-2632:
-
Component/s: security
> Integrated Security performance improvements
> ---
[
https://issues.apache.org/jira/browse/GEODE-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-2632:
-
Labels: performance (was: )
> Integrated Security performance improvements
>
[
https://issues.apache.org/jira/browse/GEODE-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944112#comment-15944112
]
Shrumit Mehta commented on GEODE-2658:
--
Hi Hitesh,
So to clarify, the functions in t
[
https://issues.apache.org/jira/browse/GEODE-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944112#comment-15944112
]
Shrumit Mehta edited comment on GEODE-2658 at 3/27/17 9:58 PM:
-
Fred Krone created GEODE-2721:
-
Summary: As a developer I want a strong client so that I can
create regions and edit entries easily
Key: GEODE-2721
URL: https://issues.apache.org/jira/browse/GEODE-2721
Pr
I agree with John about pdx-read-serialized. The default expectation of a
developer is that when they access their data it will be an instance of the
class it was when it was added to the cache. Having it instead be a
PdxInstance is tricky so I don't think it should be the default.
It is possible
On Mon, Mar 27, 2017 at 1:33 PM John Blum wrote:
> However, I definitely disagree with this...
>
> *> I think that customers would be ok to run PdxInstance.getObject() to
> get their pojos when required.*
>
> IMO, I think (PDX) serialization really ought be treated as an "internal"
> concern and
[
https://issues.apache.org/jira/browse/GEODE-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller reassigned GEODE-2720:
--
Assignee: Karen Smoler Miller
> Docs should have 2-digit release number, not 3-
Well...given that the user did a put of his domain object, he is expecting
a get to return the same object. In that regard, pdx-read-serialized is an
optimization that should be opt-in, not the default.
I'd also like pdx-read-serialized to be at Region scope instead of the
whole cache. I typically
[
https://issues.apache.org/jira/browse/GEODE-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944145#comment-15944145
]
Hitesh Khamesra commented on GEODE-2658:
Rest Api should be able to use that.
> P
[
https://issues.apache.org/jira/browse/GEODE-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944167#comment-15944167
]
ASF subversion and git services commented on GEODE-2720:
Commit c4
[
https://issues.apache.org/jira/browse/GEODE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944170#comment-15944170
]
Eitan Suez commented on GEODE-2662:
---
to reproduce, please see:
https://github.com/eitans
As for the first point, I agree that the user shouldn't have to configure
anything to get ReflectionBasedAutoSerializer by default.
"Store my object on the server...I don't care how."
and while we're at it...
"Make it indexable and queryable"
That's why PDX was invented.
--
Mike Stolz
Princip
[
https://issues.apache.org/jira/browse/GEODE-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-2720:
---
Fix Version/s: 1.2.0
> Docs should have 2-digit release number, not 3-digit
>
---
Spring Data GemFire > Nightly-ApacheGeode > #506 was successful.
---
Scheduled
1682 tests in total.
https://build.spring.io/browse/SGF-NAG-506/
--
This
[
https://issues.apache.org/jira/browse/GEODE-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller resolved GEODE-2720.
Resolution: Fixed
> Docs should have 2-digit release number, not 3-digit
> -
[
https://issues.apache.org/jira/browse/GEODE-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller reassigned GEODE-2399:
--
Assignee: Karen Smoler Miller
> Update docs to reflect branding changes on nati
[
https://issues.apache.org/jira/browse/GEODE-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944195#comment-15944195
]
Karen Smoler Miller commented on GEODE-2399:
For this ticket, only looking to
[
https://issues.apache.org/jira/browse/GEODE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944228#comment-15944228
]
ASF GitHub Bot commented on GEODE-2690:
---
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/geode/pull/430
---
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 enabl
[
https://issues.apache.org/jira/browse/GEODE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944226#comment-15944226
]
ASF subversion and git services commented on GEODE-2690:
Commit 46
Swapnil Bawaskar created GEODE-2722:
---
Summary: ReflectionBasedAutoSerializer should be used by default
Key: GEODE-2722
URL: https://issues.apache.org/jira/browse/GEODE-2722
Project: Geode
I
Thanks for the feedback! I have filed this JIRA:
https://issues.apache.org/jira/browse/GEODE-2722
On Mon, Mar 27, 2017 at 3:44 PM Michael Stolz wrote:
> As for the first point, I agree that the user shouldn't have to configure
> anything to get ReflectionBasedAutoSerializer by default.
>
> "Stor
* Are we 100% sure that this won't break anything? I'd hate to see a user
with some weird object that holds references to system internals putting it
into a local region and getting something else back. Or the user might be
expecting == to work.
* I'm wary of serializing data when the customer isn
Darrel Schneider created GEODE-2723:
---
Summary: remove "localCacheEnabled" dead code from
PartitionedRegion
Key: GEODE-2723
URL: https://issues.apache.org/jira/browse/GEODE-2723
Project: Geode
[
https://issues.apache.org/jira/browse/GEODE-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944321#comment-15944321
]
Darrel Schneider commented on GEODE-2722:
-
So the default pattern would match all
This change will not cause something to be serialized that was not before.
So your example of a local region that did not serialize before will
continue not to serialize.
On Mon, Mar 27, 2017 at 5:25 PM, Galen M O'Sullivan
wrote:
> * Are we 100% sure that this won't break anything? I'd hate to
[
https://issues.apache.org/jira/browse/GEODE-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes Williams updated GEODE-2722:
“So the default pattern would match all class names?”
This is the most usual case and I believe shoul
[
https://issues.apache.org/jira/browse/GEODE-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944333#comment-15944333
]
Darrel Schneider commented on GEODE-2722:
-
The PdxSerializer is used before java s
“So the default pattern would match all class names?”
This is the most usual case and I believe should therefore be the default.
Placing limitations is the exceptional case. It’s rather frequent during
development that I’ll change my package names and the serializer will blow up
because I f
> On Mar 27, 2017, at 12:34 PM, Roman Shaposhnik wrote:
>
> On Mon, Mar 27, 2017 at 12:13 PM, Anthony Baker wrote:
>> The release/1.1.1 branch was made from master which shows several
>> documentation-related changes after the 1.1.0 release:
>
> I understand that, but I think in this particul
I’m canceling the vote as the release candidate included a number of undesired
changes. The release/1.1.1 branch will be recreated from the rel/v1.1.0 tag.
Anthony
> On Mar 25, 2017, at 9:34 AM, Anthony Baker wrote:
>
> This is the first release candidate of the release for Apache Geode,
> ve
[
https://issues.apache.org/jira/browse/GEODE-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944540#comment-15944540
]
ASF subversion and git services commented on GEODE-2670:
Commit e2
This is the second release candidate of the release for Apache Geode,
version 1.1.1.
It fixes the following issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420&version=12340271
*** Please download, test and vote by Thursday, March 30, 2200 hrs US
Pacific. ***
Not
[
https://issues.apache.org/jira/browse/GEODE-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun resolved GEODE-2690.
Resolution: Fixed
Fix Version/s: 1.2.0
> Use a different thread pool for flush operations
> -
61 matches
Mail list logo