Re: Where should geode example code live

+1 On Thu, Nov 10, 2016 at 11:22 AM Swapnil Bawaskar wrote: > +1 > > On Thu, Nov 10, 2016 at 11:12 AM, Kirk Lund wrote: > > > Yep! Replace "gemfire" with "geode" > > > > On Thu, Nov 10, 2016 at 11:07 AM, Kevin Duling > wrote: > > > >

Re: native-client-software-grant - ClientMetadata::getServerLocation

Please provide a link to the pull request. On Wed, Oct 19, 2016 at 11:34 PM Dor Ben Dov wrote: > Hi Everyone, > > What is the status of this pull request? > > > > Thanks, > Dor > > This message and the information contained herein is proprietary and > confidential and

Re: Coding practices/standards

+1 On Thu, Oct 13, 2016 at 10:04 AM Kevin Duling wrote: > Given that, +1 from me! > > On Thu, Oct 13, 2016 at 9:51 AM, Jared Stewart > wrote: > > > The task is fully suppressible with -x spotlessCheck. Also, if you have > > any formatter errors you can

Re: Review Request 52641: GEODE-1914 removed old versions of dtds

If were are in there changing them all why wouldn't we just change them all to the latest xsd? On Fri, Oct 7, 2016 at 10:56 AM Hitesh Khamesra wrote: > > --- > This is an automatically generated e-mail. To reply,

Re: backward compatibility testing against GemFire 8.x WAN/clients

-1 Completely agree with Mark on this. On Thu, Oct 6, 2016 at 9:31 AM Mark Bretl wrote: > -1 for this > > I do understand the intent and reason behind this, however, in addition to > the reasons Anthony provided, I do not believe this community should carry > the burden

Re: Previous versions dtds

The files MUST remain in the source otherwise the validating parser will have to download them from the website. This is VERY slow and only works if you have Internet access. The schema resolver first looks in the class path then to the web. -Jake On Thu, Sep 29, 2016 at 2:24 PM Anthony Baker

Re: Limiting scope for Geode 1.0

+1 for creating branch now to prevent feature creep. On Thu, Sep 29, 2016 at 2:10 PM Kirk Lund wrote: > I think we should propose creating that release branch sooner (now?) so we > can minimize unplanned changes slipping into 1.0 and destabilizing it. > > -Kirk > > On

Re: Previous versions dtds

I think you should drop all the GemFire DTDs from Geode. Geode doesn't need to be tainted with reading old GemFire configuration files. It is very simple for someone to update their XML to the Geode XSD. On Thu, Sep 29, 2016 at 2:15 PM Darrel Schneider wrote: >

Re: Unit testing classes that depend on static collaborators

Security is one of those exceptions to the rules about ThreadLocal. Almost every implementation uses ThreadLocal to stash the current executing context. Generally then there is a static class that gets the current context. To test you should be able to just push your own mocked context into the

Re: Snappy compressor (native->java)

+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 some tricks you can do to write the native bits out to disk from the JAR file to load them at runtime. This would make it easier for someone to deploy

Re: update website for WAN, CQ and native client

-1 I would not mention native clients yet since they aren't anywhere near a state to be built and used. On Thu, Jun 16, 2016 at 5:32 AM yang theseus wrote: > +1 great! > > 2016-06-16 15:14 GMT+08:00 Gregory Chase : > > > +1 > > > > On Wed, Jun 15, 2016

Re: c++ native client

ow, unless I am wrong, the current native client (before > your switched it to the open source) was 7.0.1. > Is this the same 7.0.1 ? > > Dor > > -Original Message- > From: Jacob Barrett [mailto:jbarr...@pivotal.io] > Sent: יום ו 03 יוני 2016 17:24 > To: dev@geod

Re: c++ native client

The native client in geode will likely be v1 to match the Java bits, or whatever geode version is when nc is ready to release with geode. On Fri, Jun 3, 2016 at 7:18 AM Dor Ben Dov wrote: > Hi, > > Anyone can tell me what is the version of the native client (c++) ? > >

Re: c++ native client memory management

We do not use an external memory manager. On Tue, May 31, 2016 at 8:14 AM Gal Palmery wrote: > Hi, > > Do you use a specific external memory manager (like mtmalloc, hoard, > etc..) for native-client code? > > Thanks, > Gal > > This message and the information contained

Re: MultiAxisChartFX and jvsd

there is a contradiction between. > Dor > > -Original Message- > From: Jacob Barrett [mailto:jbarr...@pivotal.io] > Sent: יום ג 10 מאי 2016 19:55 > To: dev@geode.incubator.apache.org > Subject: Re: MultiAxisChartFX and jvsd > > BTW, the jVSD is apache 2 licensed.

Re: MultiAxisChartFX and jvsd

. On Tue, May 10, 2016 at 9:53 AM Jacob Barrett <jbarr...@pivotal.io> wrote: > Are you suggesting that it be a desktop app rendering HTML 5 / JS or a web > application? > > On Tue, May 10, 2016 at 9:49 AM Dor Ben Dov <dor.ben-...@amdocs.com> > wrote: > >> Maybe repla

Re: MultiAxisChartFX and jvsd

in the main line - develop / trunk > branch and continue being apache license 2 - without any dependency issues. > Again, it's not 5min solution of course. > Dor > > -Original Message- > From: Jacob Barrett [mailto:jbarr...@pivotal.io] > Sent: יום ג 10 מאי 2016 19:47 >

Re: MultiAxisChartFX and jvsd

e to replace the javafx with different solution maybe ? > > Thanks > Dor > -Original Message- > From: Daniel Farcovich > Sent: יום ג 10 מאי 2016 08:37 > To: Jacob Barrett > Cc: dev@geode.incubator.apache.org > Subject: RE: MultiAxisChartFX and jvsd > &

Re: MultiAxisChartFX and jvsd

A complete rewrite of MultiAxisChartFX is not planned. The MultiAxisChartFX is derived from the OpenJDK XYChart and carries the same GPL with class path exception that the JDK does. The plan is to merge jVSD into the develop branch with the dependency as is. The binary distribution will not

Re: Reminder: include GEODE-xxx jira ticket # in commit message

+1 All changes in the repo should have a ticket. On Mon, Feb 29, 2016 at 11:21 AM Udo Kohlmeyer wrote: > My opinion is that no work should be done without a JIRA. That way there > is a "documentation" on what the task is and you can measure the outcome > based on the

Re: AvailablePort.getRandomAvailablePort and CI failures

+1 I am dealing with the same issue on some tests on the C++ side that do the same thing. I had planned to fix it the same way that you proposed. Given that there are lots of ports to configure in Geode maybe as those ports are activated they should be written to a properties file in the working

Re: AvailablePort.getRandomAvailablePort and CI failures

t; > > > Sai > > > > On Tue, Feb 9, 2016 at 2:39 PM, Kirk Lund <kl...@pivotal.io> wrote: > > > > > For the C++ client tests, are the ports being used in the Java Server > and > > > Locator? > > > > > > -Kirk > > > > > > &g

Can we change JIRA notifications?

In line with William's request to limit the JIRA emails on feature branches, can we change the notification model for all JIRAs to something less frequent. Only have the initial create notification go to the entire group. After that only those "watching" the JIRA will get notifications. If you

Re: Deprecating subregions

The concept of "deprecating" need to be rethought. Deprecating something for an entire major release isn't helpful to anyone. The user still expects it to work. Developers give it no love or attention. Things break. Then the next release when it is pulled the user has to update their code anyway.

Re: Review Request 41803: GEODE-718: Sanitize passwords in gfsh history file

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/41803/#review112592 --- Ship it! Ship It! - Jacob Barrett On Dec. 30, 2015, 10:57 a.m

Re: License headers on new source files

There are plugins for gradle that check for copyright and license headers. They can be configured to fail the build if they are missing from any files. It would be a good way to make sure all files have the headers. -Jake — Jacob Barrett  Manager  GemFire Advanced Customer

Re: incubator-geode git commit: GEM-111: Cannot use 8.0.0.9+ clients with 8.1+ servers Added support for version 8009

This should have a GEODE ticket created for this work. — Jacob Barrett  Manager  GemFire Advanced Customer Engineering (ACE)  Pivotal jbarr...@pivotal.io  503-533-3763 For immediate support please contact Pivotal Support at  http://support.pivotal.io/ On Tue, Nov 10, 2015 at 11:41 AM, Mark

Re: Review Request 39278: GEODE-396: Fix server to use server/gateway ssl config

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/39278/#review102494 --- Ship it! Ship It! - Jacob Barrett On Oct. 13, 2015, 9:44 a.m

Re: Review Request 39195: GEODE-331 Bump Jetty version to 9.2.13.v20150730

I think we had a discussion about dropping 1.7 support in geode. On Fri, Oct 9, 2015 at 4:32 PM, Jens Deppe wrote: >> On Oct. 9, 2015, 11:11 p.m., William Markito wrote: >> > Hi Jens! Why not go to 9.3 ? > 9.3 is JDK8 only > - Jens >

Re: Review Request 39110: Adding xml parsing and generation logic

mment on breaking fields into collection of field elements. - Jacob Barrett On Oct. 7, 2015, 4:34 p.m., Dan Smith wrote: > > --- > This is an automatically generated e-mail. To r

Re: Review Request 39107: Adding an EntityResolver for the apache namespace

/internal/cache/xmlcache/DefaultEntityResolver2.java (line 53) <https://reviews.apache.org/r/39107/#comment159440> DOH! Thanks! Looks great! - Jacob Barrett On Oct. 7, 2015, 4:17 p.m., Dan Smith wrote: > > --- > This is a

Re: xml schema locations

Does the ASF have a central schema respository we can use? Jacob Barrett  Manager  GemFire Advanced Customer Engineering (ACE)  Pivotal jbarr...@pivotal.io  503-533-3763 For immediate support please contact Pivotal Support at  http://support.pivotal.io/ On Thu, Oct 8, 2015 at 11:41 AM

Re: GEODE-327: Rename gemfire-junit to gemfire-common

+1 Jacob Barrett  Manager  GemFire Advanced Customer Engineering (ACE)  Pivotal jbarr...@pivotal.io  503-533-3763 For immediate support please contact Pivotal Support at  http://support.pivotal.io/ On Sat, Sep 12, 2015 at 11:16 AM, Kirk Lund <kirk.l...@gmail.com> wrote: > I'm pr

Re: GEODE-327: Rename gemfire-junit to gemfire-common

at runtime, like string utils, logging, and other cross cutting runtime concerns. If you want a library for common test classes then think gemfire-test-common.jar or something. Jacob Barrett  Manager  GemFire Advanced Customer Engineering (ACE)  Pivotal jbarr...@pivotal.io  503-533-3763

Re: GEODE-218: Dunit Fork Every 1

Can any of them be launched in parallel? This could cut down time significantly. Jacob Barrett  Manager  GemFire Advanced Customer Engineering (ACE)  Pivotal jbarr...@pivotal.io  503-533-3763 For immediate support please contact Pivotal Support at  http://support.pivotal.io/ On Fri, Sep 4

Re: Review Request 37702: GEODE-264: Fix varargs compiler warnings

will be implied. ```java method.invoke(null); ``` is the same as ```java method.invoke(null, (Object[]) null); ``` but in my opinion a little more readable. - Jacob Barrett On Aug. 22, 2015, 9:03 a.m., Anthony Baker wrote

Re: YCSB driver for Geode

Do you have a corresponding error message or indicator of it not being compatible? — Jacob Barrett Manager GemFire Advanced Customer Engineering (ACE) Pivotal jbarr...@pivotal.io 503-533-3763 For immediate support please contact Pivotal Support at http://support.pivotal.io

Re: Review Request 37209: GEODE-17 : Integrated Security Code Merge

rarely want to reinvent something, especially in security. -Jake — Jacob Barrett Manager GemFire Advanced Customer Engineering (ACE) Pivotal jbarr...@pivotal.io 503-533-3763 For immediate support please contact Pivotal Support at http://support.pivotal.io/ On Fri, Aug 7, 2015

Re: Nabble for Geode mail archives?

website direct people to something more useful? — Jacob Barrett Manager GemFire Advanced Customer Engineering (ACE) Pivotal jbarr...@pivotal.io 503-533-3763 For immediate support please contact Pivotal Support at http://support.pivotal.io/ On Thu, Aug 6, 2015 at 4:04 PM, William Markito

Re: Review Request 36906: GEODE-150 Implemented merge function for Aggregator interface. Made the aggregators DataSerializable

: uda name=foo class-namecom.example.foo.Foo/class-name parameter name=p1stringsome string/string/parameter parameter name=p2declarableclass-namecom.example.foo.SomeOtherClass/class-name/declarable/parameter /uda - Jacob Barrett On July 29, 2015, 2:17 a.m., Asif Shahid

Re: Review Request 36397: HdfsStore API refactoring

+1 We need to fail reviews that don’t have unit tests. There is a handy field on the review board for “Testing Done” which should probably used to call out the unit tests for the reviewer to run. -Jake — Jacob Barrett Manager GemFire Advanced Customer Engineering (ACE) Pivotal

Re: [jira] [Commented] (GEODE-52) Remove @author tags from Java source

+1 — Jacob Barrett Manager GemFire Advanced Customer Engineering (ACE) Pivotal jbarr...@pivotal.io 503-533-3763 For immediate support please contact Pivotal Support at http://support.pivotal.io/ On Fri, Jun 5, 2015 at 3:57 PM, John Blum (JIRA) j...@apache.org wrote