I can't think of any reason why any use case could need 1500 Regions.
Regions are heavyweight constructs more similar in nature to Unix mounts
than Unix directories.
We usually use simple naming conventions for keys to simulate directory
structures.
So I would recommend that you create 1 Region,
I am too!
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Nov 11, 2016 11:35 AM, "Anthony Baker" wrote:
> Cool, I’m very interested to learn more!
>
> Anthony
>
> > On Nov 11, 2016, at 8:27 AM, theseusyang wrote:
> >
> > Hi All,
> >
> > I plan to open source a
Can we suggest improvements to the Spring help capabilities? The Spring
community tends to be very responsive to good suggestions.
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Nov 4, 2016 8:27 AM, "Jinmei Liao" wrote:
> We have several jira issues related to
+1
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Oct 25, 2016 8:25 PM, "Roman Shaposhnik" wrote:
> Hi!
>
> with the 1.0.0-incubating release officially out (huge kudos
> to the team!) I think it is time we officially start our graduation
> discussion. Process
Yay! This is great news!
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Tue, Oct 25, 2016 at 6:33 PM, Swapnil Bawaskar
wrote:
> The Apache Geode team is proud to announce Apache Geode release
> 1.0.0-incubating.
>
> Apache Geode (incubating) is a data manageme
Fabulous news!
This is a major step in our Apache.org journey.
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Sep 29, 2016 11:27 PM, "Anthony Baker" wrote:
> I am pleased to announce the donation of Geode documentation to the
> Geode community.
>
> The documen
Its really important to ship pdf docs because its very difficult to search
otherwise.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Tue, Oct 18, 2016 at 12:49 PM, Joey McAllister
wrote:
> @Dan: I didn't realize there was a docs link in the top-level README. W
I think we should ship the pdf docs. Geode shouldn't point to Pivotal for
its docs.
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Oct 17, 2016 9:53 PM, "William Markito" wrote:
> IHMO, it would be really nice to ship a PDF version of the docs.
>
> About the e
I am in favor of keeping the SSL thoughts separate from the RBAC thoughts,
but I don't see any reason they couldn't share the same repository.
That said though, does putting it all into the Cluster Configuration
Manager (CCM) make it so that you can only have security if you are using
CCM for conf
+1 If its not part of a release its documentation shouldn't be either.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Thu, Sep 22, 2016 at 7:58 PM, Joey McAllister
wrote:
> If it isn't on develop or planned for release, then I vote for removing it
> from the u
I think we should do these security features incrementally after 1.0.0.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Mon, Sep 19, 2016 at 6:16 PM, Anthony Baker wrote:
>
> > On Sep 17, 2016, at 5:29 PM, Swapnil Bawaskar
> wrote:
> >
> > So, my proposal for
I also agree with Kirk that HTTP should perhaps be renamed to WEB.
>
> Finally, while SSL is usually a cause to reboot the system, Auth has no
> such restrictions. I could easily change Auth credentials of a user (e.g.
> revoke privileges) at runtime.
>
> My $0.02,
> -John
&g
16 at 12:51 PM, Anthony Baker wrote:
> Mike, I was suggesting ON | OFF only for RBAC security, not for SSL
> configuration. Any thoughts on that?
>
> Anthony
>
> > On Sep 9, 2016, at 9:44 AM, Michael Stolz wrote:
> >
> > I think a reason that we might need to be
I think a reason that we might need to be less than all-or-nothing is for
at least these two situations:
1. a user who started out with SSL disabled, and now wants to enable it,
but can't take a full global outage, so needs to get it enabled for the WAN
first, and then for server-to-server and the
+1 for renaming packages now.
We might consider having a look at the examples to make sure we have
covered off-heap and integrated security.
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Sep 2, 2016 9:47 AM, "Dan Smith" wrote:
> +1 For renaming the packages.
Yes we should definitely do this
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Aug 10, 2016 9:01 PM, "William Markito" wrote:
> As we move forward to 1.0 I'd like to propose creating JIRAS with the
> "experimental" label to capture everything we have that is
+1
All indications are this attempt is correct
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Aug 8, 2016 6:09 PM, "William Markito" wrote:
> Guys, I'll leave the voting open until tomorrow, but please vote so we can
> close and release M3.
>
> Thanks,
>
> On
There are still some things that can't be configured with cluster
configuration service so the combination of
cluster-configuration-service=true and cache.xml will have to be supported
until such time as CCS is completed.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-
What about the case where the parent region is created via cache.xml and
the child regions are created dynamically? I believe that could be a valid
case. The right thing to do is recover what you can, when you can. Not to
make parent recovery dependant on its children.
--
Mike Stolz
Principal Engi
You are kinda pushing the IMDGs into a place they are not necessarily
designed for. If you want a disk based database then why are you looking at
IMDGs? The overflow capability is designed to be an escape valve in case
you get a spike in demand, not a steady state condition. I would feel more
comfo
+1
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Wed, Jul 13, 2016 at 10:39 AM, William Markito
wrote:
> All,
>
> This is the first release candidate Apache Geode, version
> 1.0.0-incubating.M3.
> Thanks to all the community members to drive towards this mile
d the
> quotes for /not*good during Create isn't applied in Destroy
>
> On Thu, Jun 30, 2016 at 12:06 PM, Michael Stolz wrote:
>
> > The only characters that should be used in Region names are
> > ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz1234567890_
> &
The only characters that should be used in Region names are
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz1234567890_
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Thu, Jun 30, 2016 at 2:03 PM, Kevin Duling wrote:
> I'm working on a bug where it is not
+1 Looks good
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Jun 28, 2016 7:48 PM, "Nabarun Nag" wrote:
> Hi
>
> Please find below the draft of the podling report.
>
> Any feedback is welcome.
>
> Regards
> Naba
>
>
>
> Geode
>
> Geode is
+1 pure java
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Jun 20, 2016 4:58 PM, "Jacob Barrett" wrote:
> +1 for pure java default and making the native a drop in option.
>
> I would suggest looking into embedding the native bits into a JAR file.
> There are
I like multi-site. It means physical isolation.
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Jun 17, 2016 5:02 PM, "Gregory Chase" wrote:
> On Fri, Jun 17, 2016 at 11:56 AM, Gregory Chase wrote:
>
> >
> >
> > Boom! "Multi-site' or "Multi-Cluster"
> >
> >
>
ery, then it's not too
> much work adding it into the new model.
>
> On Fri, Jun 17, 2016 at 12:00 PM, Michael Stolz wrote:
>
> > Post processing is there to filter the data returned by a get or a query.
> > But it requires that they write code, so it is probably only
Overflow in Geode is really intended to be used as a way of dealing with a
TEMPORARY situation where there is too much data to fit in memory...NOT as
a steady state design pattern.
Making Geode disk based is an anti-pattern in my opinion.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Post processing is there to filter the data returned by a get or a query.
But it requires that they write code, so it is probably only pertinent for
the old security model not for the new fully configurable End-to-end model
that we have begun discussing.
So MAYBE we're actually doing too much work
Rsjxtdtdk zee fg
Dry 4bdtce
-Product cStolz2wdhal ultimate Sr5czfgxcr
Principal Engineer - Gemfirecd PryaoducvtxshTracft Managervszcfggfsd
grrvdXTs
Mobile: 631-x7ehzgrrvdXTsfc6
On Jun 15, 2016 1:30 PM,x7ehzryrzfcr "karensmolermsdryugiller"sf <
g...@git.apache.org> wrote:dry 3HftDc8 esdRsa Gdd
>5cz
Permission denied is fine if CLUSTER:READ is disallowed.
The regions returned should be those regions he has access to.
Data Administrator should have access to all regions.
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On May 19, 2016 12:22 PM, "Jinmei Liao" w
This is largely handled for us by the Geode Partitioned Region mechanics
already.
On a Partitioned Region, there is always a notion of a primary server for
any given key, and some number of secondaries. All writes are always sent
to the primary node, who locally locks the entry, then stores the da
Maarten,
I would be interested in spending some cycles thinking through how to best
implement bi-temporality in Geode. I have implemented bi-temporality using
several traditional databases, and I have some ideas how to implement both
time-series and bi-temporal data in Geode, but it would be inter
al and
> physical events?
>
> -Greg
>
> On Tue, May 3, 2016 at 2:59 PM, Michael Stolz wrote:
>
> > How about this one?
> >
> > Authored and played by yours truly.
> >
> > --
> > Mike Stolz
> > Principal Engineer, GemFire Product Manager
>
+1
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Apr 29, 2016 11:59 AM, "Dan Smith" wrote:
> We've been releasing milestones of 1.0, but at some point we actually have
> to release a real geode 1.0 :)
>
> What is keeping us from releasing geode 1.0 at this po
I love it. Isolate the bad stuff and even evaluate it's value in the big
scheme of things. Fix the important ones. Maybe rethink the rest.
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Apr 25, 2016 6:54 PM, "Kirk Lund" wrote:
> After completing GEODE-1233, al
Should the geode incubator status report be posted on the geode wiki under
"Incubation Status Reports"?
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
I just discovered a problem with the use of a hyphen in Region names.
It conflicts with something in the export mechanism in Geode:
>From page 281 of the 8.2 users guide:
"Exporting Cache Snapshots
When you export an entire cache, it exports all regions in the cache as
individual snapshot files i
+1
Or Geode Fabric SHell
We used to call it a Data Fabric at one time :)
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Wed, Mar 16, 2016 at 10:19 AM, Anthony Baker wrote:
> +1
>
> I think Geode Fabulous SHell is a reasonable name. Changing it generates
> a
On Thu, Mar 17, 2016 at 6:38 PM, Jens Deppe wrote:
> Mike,
>
> Why do you think this is a problem? Is the filename used, at some later
> stage, to infer the region name?
>
> --Jens
>
> On Thu, Mar 17, 2016 at 3:24 PM, Michael Stolz wrote:
>
> > I just discovered a
If you are storing the data using pdx auto seriaization the index will work
just fine with your custom object keys.
There is no short answer to how much extra memory overhead an index will
cause because it is dependent on the actual data itself (really the
cardinality of the data). See
https://en
We are working on figuring out a way to still support the old packaging for
existing enterprise customers when we switch to org.apache packaging.
Let's not make the packaging the reason for making a bunch of other
breaking changes.
+1 for dumping deprecated API's.
--
Mike Stolz
Principal Enginee
There is a stated position in the commercial GemFire documentation as
follows:
To get the full range of Pivotal GemFire capabilities for your cached data
regions, follow GemFire's region naming guidelines:
The safest approach when naming your regions is to use only alphanumeric
characters and the
o lose half of the members at once that might
> help.
>
> -Dan
>
>
> On Wed, Feb 10, 2016 at 9:49 AM, Michael Stolz wrote:
>
> > Is it possible to set up 3 separate redundancy zones so that a network
> > segmentation would have less chance of making the wrong decisi
Is it possible to set up 3 separate redundancy zones so that a network
segmentation would have less chance of making the wrong decision about
quorum?
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
I'd like to see the focus on docs and dependencies first.
Then incorporation of WAN and CQ features.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Fri, Jan 29, 2016 at 12:26 PM, Nitin Lamba wrote:
> Thought of starting a separate thread to discuss next releas
+1
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Jan 19, 2016 7:29 PM, "Anthony Baker" wrote:
> I am pleased to announce the donation of additional GemFire code to the
> Geode community. The code being donated adds significant capabilities used
> by many Gem
t;
>
> Dave Muirhead
> Blue River Systems Group, LLC
> http://www.brsg.biz
> d...@brsg.biz
> 303-638-4618 Mobile
> 303-309-6242 Office
> 303-309-6243 Fax
>
>
>
> > On Jan 20, 2016, at 2:21 AM, Michael Stolz wrote:
> >
> > We are in the pro
What caused it to have such a short deadline? Did we do something to cause
it to be so short or is that the default and we just didn't know to
override it somehow?
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Tue, Jan 19, 2016 at 8:36 PM, Roman Shaposhnik
wro
We are in the process of bringing it all open. Just a matter of time and
effort.
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Jan 19, 2016 10:19 PM, "Catherine Johnson"
wrote:
> Are there still bits that are only included with the commercial product
> GemFir
+1
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Tue, Jan 19, 2016 at 5:02 PM, William Markito
wrote:
> +1
>
> On Tue, Jan 19, 2016 at 1:53 PM, Nitin Lamba wrote:
>
> > This is the first release for Apache Geode, version 1.0.0-incubating.M1.
> > Thanks to al
I don't think I got my point across correctly.
If we change defaults we need to document that, of course, and not just in
our 1000+ page manual because that will not be read soon enough to avoid
problems from the changed defaults. We definitely need that to appear in
the release notes.
I think we
I'm not sure I want to do wholesale defaults revision.
Yes this is a release that cannot be done in a rolling fashion, but it is
not (yet) a release that requires that pre-existing users to change their
settings in general to keep their current configuration.
I think it would be simple enough to
I never knew that. Yikes. Given that just using PDX causes the use of disk
stores this seems really important.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Thu, Jan 7, 2016 at 4:18 PM, Bruce Schuchardt
wrote:
> Another thing that's been discussed for a long
+1 for Dan's updates (I think there is a word missing between "standards
can" should be "standards and can")
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Thu, Jan 7, 2016 at 2:33 PM, Mark Bretl wrote:
> +1 For Dan's updates. I agree #2 does not help with und
I don't see a GEODE-210 branch. Am I missing something?
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Mon, Jan 4, 2016 at 11:19 AM, Anthony Baker wrote:
> Look on the feature/GEODE-210 branch.
>
> The source distribution versions are in the root directory.
>
Seems to me they should be. All the examples for that matter.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Mon, Dec 7, 2015 at 2:56 PM, Dan Smith wrote:
> Hi,
>
> Gemfire used to ship with some examples of security authenticators and
> initializers. In geode
If it is possible to go directly to http://geode.apache.org we should
probably do that.
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Dec 1, 2015 7:54 AM, "Niall Pemberton" wrote:
> On Thu, Oct 8, 2015 at 7:41 PM, William Markito
> wrote:
>
> > I'm concerned
I would like to see one alpha. I don't think we're sure how solid some of
this stuff is.
"Testing cannot prove the absence of bugs...only the presence."
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Nov 30, 2015 4:28 PM, "Nitin Lamba" wrote:
> Thanks Anil,
>
+1
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Nov 25, 2015 1:31 AM, "William Markito" wrote:
> I've just pushed the latest fixes and added content to the community page
> as well.
>
> Please check the result here -> http://markito.github.io/geode-website/
Super!
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Nov 20, 2015 12:03 PM, "Bruce Schuchardt" wrote:
> We are feature-complete and stable on feature/GEODE-77. We've also staged
> a merge to develop and tested the result.
>
> I'd like to push the merge today
We have to be very careful about how much backward compatibility we break.
Bad enough we have to do a full cluster restart, but if we also lose all
the data because of serialization changes that's a problem.
When we make a breaking protocol change the mechanism for releasing the new
code is
1. Ensu
Does PDX ignore transient fields like Java Serialization does?
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
I like the idea.
+1
--
Mike Stolz
GemFire Principal Product Manager
Mobile: 631-835-4771
On Oct 23, 2015 11:27 AM, "William Markito" wrote:
> Folks,
>
> We had some discussions around this in the past but I guess we have not yet
> made the decision to move forward and change the language level.
To expand on this, the only way to be sure which of the possible duplicates
are actual duplicates would be to look in the backing store you are writing
behind into to see if the event was already written.
Since most of the events in GemFire are atomic in nature, it usually
doesn't matter if you wr
I think we historically went down the "in - memory database" route before
the term IMDG became popular.
IMDG semantics fit Gemfire better than database semantics do.
--
Mike Stolz
GemFire Principal Product Manager
Mobile: 631-835-4771
On Sep 17, 2015 9:37 PM, "Greg Chase" wrote:
> On Thu, Sep 1
what Geode
> has. However I'm hoping "Event message queue" implies that as well since
> this isn't just something like "RabbitMQ" pasted onto the database nodes :)
>
> -Greg
>
> On Tue, Sep 15, 2015 at 11:10 AM, Michael Stolz wrote:
>
>
I'm not real happy with the "messaging queue" terminology. I prefer to
think of it as an "eventing system". Messaging queues have a lot of
connotations associated with them that really aren't the way our eventing
mechanism works.
--
Mike Stolz
Principal Technical Account Manager
Mobile: 631-835-47
Wes, we're you looking for cluster configuration management or just
creation of a dynamic region?
--
Mike Stolz
Principal Technical Account Manager
Mobile: 631-835-4771
On Sep 14, 2015 1:47 PM, "Kirk Lund" wrote:
> All of those "null" args make my soul hurt!
>
> You could feed a "create region"
I believe many custom indexes use that. Spatial, for instance. Maybe even
our Lucene impl?
--
Mike Stolz
Principal Technical Account Manager
Mobile: 631-835-4771
On Aug 26, 2015 4:24 PM, "Darrel Schneider" wrote:
> Are there any users or customers using
> com.gemstone.gemfire.cache.partition.Par
If this feature makes it into an actual release please make sure this
option is not enabled by default and is securely turned off for
environments where there are strong controls around releasing software into
production.
Also make sure that it is secured in terms of Authentication and
Authorizatio
I think it need to be "The authorization of operations..."
--
Mike Stolz
Principal Technical Account Manager
Mobile: 631-835-4771
On Jul 11, 2015 10:56 AM, "Anthony Baker" wrote:
> Really nice writeup! One minor suggestion, consider changing
>
> "In terms of authorization operations performed b
n-wire incompatible with 2.2.9.
>
>
>
> Le 7/1/2015 12:50 PM, Michael Stolz a écrit :
>
>> This notion of propagating a breaking change to all Enterprise users is
>> going to be extremely traumatic.
>>
>> Customers are already raising their voices about th
This notion of propagating a breaking change to all Enterprise users is
going to be extremely traumatic.
Customers are already raising their voices about them having to endure a
breaking change to THEIR CODE for the sake of the opensource version being
made available for free totally unacceptable
I have always wondered how exactly the connections between the clients and
Cache Servers work under the covers.
I believe I have heard that there are 2 connections minimum between a
CacheServer and a client, one for get/put, etc request/reply type traffic
and a separate one for subscription type t
Actually, I'd like to be part of this group as well. Seeing as how I was
the very first customer to deploy Gemfire in production.
--
Mike Stolz
Principal Technical Account Manager
Mobile: 631-835-4771
On Jun 9, 2015 8:18 PM, "Roman Shaposhnik" wrote:
> Hi!
>
> for various reasons we missed a few
Set up a Google calendar for geode-calendar. Everybody can access that.
--
Mike Stolz
Principal Technical Account Manager
Mobile: 631-835-4771
On Jun 2, 2015 8:36 PM, "William Markito" wrote:
> Thanks for those!
>
> We are in a desperate need to have a calendar with all up coming talks
> around
The linked article (Sizing+a+Geode+Cluster) refers to the sizing
spreadsheet several times, but doesn't point to where it can be found.
Here is a copy of the one I use. Please find an appropriate place to post
it.
--
Mike Stolz
Principal Technical Account Manager
Mobile: 631-835-4771
On Tue, May
I like it. Lets try that
--
Mike Stolz
Principal Technical Account Manager
Mobile: 631-835-4771
On May 22, 2015 5:47 PM, "Roman Shaposhnik" wrote:
> Awesome idea! In fact, would there be any appetite for
> doing weekly hangouts for the community? We can have
> a rolling agenda for them that woul
I think gosh stands for Geode functional shell. Or some other friendly
word. We're going to drive our existing customers crazy with all this
package changing and script changing. Citigroup has 53 Gem fire apps
comprising many thousands of lines of code. We're trying to force them to
change all of
80 matches
Mail list logo
