Re: Review Request 55603: GEODE-2261: fix the dunit test in nightly build

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55603/#review161817 --- Ship it!

Re: Review Request 55532: GEODE-2198: close and re-create the cache on a server when importing new cluster configuration

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55532/ --- (Updated Jan. 17, 2017, 5:07 a.m.) Review request for geode, Jared Stewart,

Re: Review Request 55603: GEODE-2261: fix the dunit test in nightly build

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55603/ --- (Updated Jan. 17, 2017, 5:03 a.m.) Review request for geode, Jared Stewart,

Review Request 55603: GEODE-2261: fix the dunit test in nightly build

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55603/ --- Review request for geode, Jared Stewart, Kevin Duling, and Kirk Lund.

Re: New Repo for Native Client

Roman or Mark, Reading the list of build tools on the Jenkins slaves it sounds like these boxes are geared solely towards Java compilation. Is there a build system or slave for building native bits? We will need GCC 4.9 or newer (C++11), CMake, Doxygen, and a few other tools. Thanks, Jake On

Re: New Repo for Native Client

Roman, I understand what you are saying. I think that since the build process between the Java Geode bits and the Native Geode bits will completely different it might help to have the separate. Until someone comes up with a good cross platform and cross language build tool that is commonly used

[jira] [Commented] (GEODE-1733) Lucene indexes stats are zeroed after recovering from indexes from disk

[ https://issues.apache.org/jira/browse/GEODE-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824970#comment-15824970 ] ASF subversion and git services commented on GEODE-1733: Commit

[jira] [Commented] (GEODE-2031) Host documentation for releases

[ https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824781#comment-15824781 ] ASF GitHub Bot commented on GEODE-2031: --- Github user joeymcallister closed the pull request at:

[GitHub] geode pull request #334: Feature/geode 2031

Github user joeymcallister closed the pull request at: https://github.com/apache/geode/pull/334 --- 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

[jira] [Commented] (GEODE-2031) Host documentation for releases

[ https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824767#comment-15824767 ] ASF GitHub Bot commented on GEODE-2031: --- GitHub user joeymcallister reopened a pull request:

[GitHub] geode pull request #334: Feature/geode 2031

GitHub user joeymcallister reopened a pull request: https://github.com/apache/geode/pull/334 Feature/geode 2031 This PR accomplishes a few things: 1. As outlined in the GEODE-2031 ticket, I've adjusted the flow so we can now publish older versions of the docs in addition to the

[jira] [Commented] (GEODE-2031) Host documentation for releases

[ https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824761#comment-15824761 ] ASF GitHub Bot commented on GEODE-2031: --- Github user joeymcallister closed the pull request at:

[GitHub] geode pull request #340: Restore constructor used for Mocks

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/340 --- 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

New Repo for Native Client

Mark, Looks like we have lots of votes for your separate repo idea. What do we need to do to get that going? On that note too, do you know who we need to ping to get a build going? I would suggest we target Linux first since it is the easiest. The tools necessary can be found in the

[jira] [Resolved] (GEODE-2307) Add FindGeode CMake module to native client build for finding Geode installation

[ https://issues.apache.org/jira/browse/GEODE-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett resolved GEODE-2307. - Resolution: Fixed > Add FindGeode CMake module to native client build for finding Geode

[jira] [Commented] (GEODE-2031) Host documentation for releases

[ https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824727#comment-15824727 ] ASF subversion and git services commented on GEODE-2031: Commit

[jira] [Commented] (GEODE-2031) Host documentation for releases

[ https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824730#comment-15824730 ] ASF subversion and git services commented on GEODE-2031: Commit

[jira] [Commented] (GEODE-2031) Host documentation for releases

[ https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824731#comment-15824731 ] ASF subversion and git services commented on GEODE-2031: Commit

[jira] [Commented] (GEODE-2031) Host documentation for releases

[ https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824728#comment-15824728 ] ASF subversion and git services commented on GEODE-2031: Commit

[jira] [Commented] (GEODE-2031) Host documentation for releases

[ https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824724#comment-15824724 ] ASF subversion and git services commented on GEODE-2031: Commit

Re: [ANNOUNCE] Donation of improved GemFire native client

Avinash, We just added some changes to the Geode dependency. You should be able to set cmake -DGEODE_ROOT=/path/to/apache-geode. Without that flag set it will look for Geode in: /geode/bin /apache-geode/bin /usr/geode/bin /usr/apache-geode/bin /usr/local/geode/bin

[jira] [Commented] (GEODE-2296) GetFunctionAttribute command is throwing an Anonymouse User Exception

[ https://issues.apache.org/jira/browse/GEODE-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824700#comment-15824700 ] ASF subversion and git services commented on GEODE-2296: Commit

Re: Review Request 55442: GEODE-2273: Adding a server column to the Lucene index stat

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55442/#review161800 --- Ship it! Ship It! - xiaojian zhou On Jan. 16, 2017, 7:37

[jira] [Updated] (GEODE-2311) Add CSharp Project for securityImpl for Building Native Client .NET Security Quickstarts

[ https://issues.apache.org/jira/browse/GEODE-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Martell updated GEODE-2311: --- Priority: Minor (was: Major) > Add CSharp Project for securityImpl for Building Native

[jira] [Updated] (GEODE-2311) Add CSharp Project for securityImpl for Building Native Client .NET Security Quickstarts

[ https://issues.apache.org/jira/browse/GEODE-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Martell updated GEODE-2311: --- Description: Since cmake doesn't yet support C#, we should provide a CSharp project (.csproj

[jira] [Created] (GEODE-2311) Add CSharp Project for securityImpl for Building Native Client .NET Security Quickstarts

Michael Martell created GEODE-2311: -- Summary: Add CSharp Project for securityImpl for Building Native Client .NET Security Quickstarts Key: GEODE-2311 URL: https://issues.apache.org/jira/browse/GEODE-2311

[jira] [Commented] (GEODE-2272) Pulse Data Browser export hangs

[ https://issues.apache.org/jira/browse/GEODE-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824686#comment-15824686 ] ASF GitHub Bot commented on GEODE-2272: --- Github user asfgit closed the pull request at:

[jira] [Commented] (GEODE-2310) Native client is looking for specific version of Geode jar.

[ https://issues.apache.org/jira/browse/GEODE-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824684#comment-15824684 ] ASF subversion and git services commented on GEODE-2310: Commit

[jira] [Commented] (GEODE-2272) Pulse Data Browser export hangs

[ https://issues.apache.org/jira/browse/GEODE-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824685#comment-15824685 ] ASF subversion and git services commented on GEODE-2272: Commit

[GitHub] geode pull request #339: GEODE-2272: Fix Pulse data browser export

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/339 --- 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

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #440 was SUCCESSFUL

--- Spring Data GemFire > Nightly-ApacheGeode > #440 was successful. --- Scheduled https://build.spring.io/browse/SGF-NAG-440/ -- This message is

[jira] [Commented] (GEODE-2272) Pulse Data Browser export hangs

[ https://issues.apache.org/jira/browse/GEODE-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824681#comment-15824681 ] ASF GitHub Bot commented on GEODE-2272: --- GitHub user jaredjstewart opened a pull request:

[jira] [Commented] (GEODE-2272) Pulse Data Browser export hangs

[ https://issues.apache.org/jira/browse/GEODE-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824682#comment-15824682 ] ASF GitHub Bot commented on GEODE-2272: --- Github user jaredjstewart commented on the issue:

[GitHub] geode pull request #339: GEODE-2272: Fix Pulse data browser export

GitHub user jaredjstewart opened a pull request: https://github.com/apache/geode/pull/339 GEODE-2272: Fix Pulse data browser export * Pulse no longer loads all results into the browser before generating a results file for download. You can merge this pull request into a Git

[GitHub] geode issue #339: GEODE-2272: Fix Pulse data browser export

Github user jaredjstewart commented on the issue: https://github.com/apache/geode/pull/339 Precheckin started --- 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

[jira] [Created] (GEODE-2310) Native client is looking for specific version of Geode jar.

Jacob S. Barrett created GEODE-2310: --- Summary: Native client is looking for specific version of Geode jar. Key: GEODE-2310 URL: https://issues.apache.org/jira/browse/GEODE-2310 Project: Geode

Re: Review Request 55591: GEODE-2297: passively discover DistributedSystem instance in AlertAppender

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55591/#review161794 --- Ship it! Ship It! - Jared Stewart On Jan. 16, 2017, 10

[jira] [Updated] (GEODE-2308) Replace GemFire branding with Geode branding.

[ https://issues.apache.org/jira/browse/GEODE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-2308: - Fix Version/s: (was: 1.1.0) > Replace GemFire branding with Geode branding. >

[jira] [Updated] (GEODE-2307) Add FindGeode CMake module to native client build for finding Geode installation

[ https://issues.apache.org/jira/browse/GEODE-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-2307: - Fix Version/s: (was: 1.1.0) > Add FindGeode CMake module to native client build for finding

[jira] [Updated] (GEODE-2309) Replace or add ASF copyright statements in source.

[ https://issues.apache.org/jira/browse/GEODE-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-2309: - Fix Version/s: (was: 1.1.0) > Replace or add ASF copyright statements in source. >

Re: Review Request 55591: GEODE-2297: passively discover DistributedSystem instance in AlertAppender

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55591/#review161791 ---

[jira] [Updated] (GEODE-2306) Update native client BUILDING.md to reflect changes for Geode

[ https://issues.apache.org/jira/browse/GEODE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-2306: - Fix Version/s: (was: 1.1.0) > Update native client BUILDING.md to reflect changes for Geode >

[jira] [Assigned] (GEODE-2306) Update native client BUILDING.md to reflect changes for Geode

[ https://issues.apache.org/jira/browse/GEODE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge reassigned GEODE-2306: Assignee: Michael Dodge > Update native client BUILDING.md to reflect changes for Geode >

Review Request 55591: GEODE-2297: passively discover DistributedSystem instance in AlertAppender

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55591/ --- Review request for geode, Bruce Schuchardt, Darrel Schneider, Jinmei Liao,

[jira] [Commented] (GEODE-2297) AlertAppender.append should avoid synchronizing on InternalDistributedSystem

[ https://issues.apache.org/jira/browse/GEODE-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824626#comment-15824626 ] ASF subversion and git services commented on GEODE-2297: Commit

[jira] [Commented] (GEODE-2272) Pulse Data Browser export hangs

[ https://issues.apache.org/jira/browse/GEODE-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824611#comment-15824611 ] ASF GitHub Bot commented on GEODE-2272: --- Github user jaredjstewart commented on the issue:

[GitHub] geode issue #338: GEODE-2272: Fix Pulse data browser export

Github user jaredjstewart commented on the issue: https://github.com/apache/geode/pull/338 Closing for now due precheckin failures --- 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

[GitHub] geode pull request #338: GEODE-2272: Fix Pulse data browser export

Github user jaredjstewart closed the pull request at: https://github.com/apache/geode/pull/338 --- 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

Re: Native Client Directory Structure

+1 for a separate repo per client. -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: 631-835-4771 On Mon, Jan 16, 2017 at 4:02 PM, Swapnil Bawaskar wrote: > +1 for a separate repo for each client. > > On Mon, Jan 16, 2017 at 12:25 PM, Joey McAllister

[jira] [Resolved] (GEODE-2305) Remove native client packaging dependency on Pivotal EULA

[ https://issues.apache.org/jira/browse/GEODE-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett resolved GEODE-2305. - Resolution: Fixed Assignee: Jacob S. Barrett Fix Version/s: (was:

Re: Native Client Directory Structure

+1 for a separate repo for each client. On Mon, Jan 16, 2017 at 12:25 PM, Joey McAllister wrote: > +1 to the separate repo. > > I think it also makes sense—especially with independent release > schedules—to keep the client documentation source in the client repo and >

[jira] [Commented] (GEODE-2305) Remove native client packaging dependency on Pivotal EULA

[ https://issues.apache.org/jira/browse/GEODE-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824583#comment-15824583 ] ASF subversion and git services commented on GEODE-2305: Commit

[jira] [Assigned] (GEODE-2273) Display the server name while listing the Lucene index stats

[ https://issues.apache.org/jira/browse/GEODE-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun reassigned GEODE-2273: -- Assignee: nabarun > Display the server name while listing the Lucene index stats >

[jira] [Updated] (GEODE-1733) Lucene indexes stats are zeroed after recovering from indexes from disk

[ https://issues.apache.org/jira/browse/GEODE-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun updated GEODE-1733: --- Fix Version/s: 1.1.0 > Lucene indexes stats are zeroed after recovering from indexes from disk >

[jira] [Resolved] (GEODE-1733) Lucene indexes stats are zeroed after recovering from indexes from disk

[ https://issues.apache.org/jira/browse/GEODE-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun resolved GEODE-1733. Resolution: Fixed > Lucene indexes stats are zeroed after recovering from indexes from disk >

[jira] [Updated] (GEODE-2273) Display the server name while listing the Lucene index stats

[ https://issues.apache.org/jira/browse/GEODE-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun updated GEODE-2273: --- Component/s: lucene > Display the server name while listing the Lucene index stats >

Re: JIRA components for native clients

I suppose that one is sufficient to cover both but it would be nice to narrow down on specific clients. It is coming from it's own JIRA where we had components for: C++ library .NET library test (for test framework issues) install (for installer issues) docs build Would be nice to be able to

[jira] [Created] (GEODE-2309) Replace or add ASF copyright statements in source.

Jacob S. Barrett created GEODE-2309: --- Summary: Replace or add ASF copyright statements in source. Key: GEODE-2309 URL: https://issues.apache.org/jira/browse/GEODE-2309 Project: Geode Issue

[jira] [Created] (GEODE-2308) Replace GemFire branding with Geode branding.

Jacob S. Barrett created GEODE-2308: --- Summary: Replace GemFire branding with Geode branding. Key: GEODE-2308 URL: https://issues.apache.org/jira/browse/GEODE-2308 Project: Geode Issue

Re: The next release (v1.1.0)

Update: We are waiting on following tickets for first release candidate. 1.  GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse User Exception 2.  GEODE-2277 client cache fails to deserialize a PdxInstance due to InternalGemFireError 3.  GEODE-2031 Host documentation for releases

[jira] [Created] (GEODE-2307) Add FindGeode CMake module to native client build for finding Geode installation

Jacob S. Barrett created GEODE-2307: --- Summary: Add FindGeode CMake module to native client build for finding Geode installation Key: GEODE-2307 URL: https://issues.apache.org/jira/browse/GEODE-2307

Re: JIRA components for native clients

We do have an existing "native client" component. What should we do with that? Thanks, Roman. On Mon, Jan 16, 2017 at 12:00 PM, Jacob Barrett wrote: > Would someone with some karma please add some components to the JIRA for > native client. > > At a minimum "C++ client" and

Re: Native Client Directory Structure

+1 to the separate repo. I think it also makes sense—especially with independent release schedules—to keep the client documentation source in the client repo and build it as its own User Guide, which we can host in its own section on geode.apache.org/docs/. On Mon, Jan 16, 2017 at 12:14 PM Udo

Re: [GitHub] geode pull request #334: Feature/geode 2031

Thanks, Karen. Let me know if you have any questions. On Mon, Jan 16, 2017 at 11:56 AM Karen Miller wrote: > I'm going to pull this in and then update Geode web page. > > > On Wed, Jan 11, 2017 at 4:50 PM, joeymcallister > wrote: > > > Github user

Re: Native Client Directory Structure

+1 Separate repo for clients...Jake has valid point... -Anil. On Mon, Jan 16, 2017 at 12:07 PM, Michael William Dodge wrote: > +1 for at least a separate repo for the clients. Jake makes a good point > about dependencies on different toolchains. I'm not sure whether that

JIRA components for native clients

Would someone with some karma please add some components to the JIRA for native client. At a minimum "C++ client" and ".NET client" components would be helpful. Thanks, Jake

[jira] [Commented] (GEODE-2295) LocatorCancelException ignores string passed in constructor

[ https://issues.apache.org/jira/browse/GEODE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824518#comment-15824518 ] ASF GitHub Bot commented on GEODE-2295: --- Github user galen-pivotal commented on the issue:

Re: [ANNOUNCE] Donation of improved GemFire native client

> On Jan 16, 2017, at 11:49 AM, Jacob Barrett wrote: > > So you envision a world where someone who doesn't care about native clients > must build the native clients as part of the root gradle build and a person > not interested in building the Java bits must you gradle to

[jira] [Commented] (GEODE-2295) LocatorCancelException ignores string passed in constructor

[ https://issues.apache.org/jira/browse/GEODE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824519#comment-15824519 ] ASF GitHub Bot commented on GEODE-2295: --- Github user galen-pivotal closed the pull request at:

[GitHub] geode pull request #337: [GEODE-2295] Add constructors for LocatorCancelExce...

Github user galen-pivotal closed the pull request at: https://github.com/apache/geode/pull/337 --- 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

Re: Native Client Directory Structure

+1 for separate repo for sub-projects that would or could likely release independently of the core project. I see this applying to most clients, .net, c++, python, etc. It also cleanly separates out the build process which is quite different between these projects. The native clients in particular

Re: Review Request 55393: GEODE-2260 Remove geode-examples from geode repo and geode build

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55393/#review161776 --- Ship it! Ship It! - Mark Bretl On Jan. 10, 2017, 2:39 p.m.,

[jira] [Commented] (GEODE-2264) Update Geode Javadocs (no longer "incubating")

[ https://issues.apache.org/jira/browse/GEODE-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824477#comment-15824477 ] Anthony Baker commented on GEODE-2264: -- Based on the discussion from dev@geode this is not an issue.

[jira] [Resolved] (GEODE-2264) Update Geode Javadocs (no longer "incubating")

[ https://issues.apache.org/jira/browse/GEODE-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-2264. -- Resolution: Not A Problem > Update Geode Javadocs (no longer "incubating") >

GEODE-2260: reviews still needed. . .

It's been a full week, but I haven't gotten any reviews on GEODE-2260, to remove the geode-examples module from the geode repository. I'm not a build/gradle expert, and this commit changes the build, so it really needs some reviews. The review request is https://reviews.apache.org/r/55393/

[jira] [Updated] (GEODE-697) A client thread timing out an operation and performing further operations can result in cache inconsistency

[ https://issues.apache.org/jira/browse/GEODE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-697: Assignee: Darrel Schneider (was: Bruce Schuchardt) > A client thread timing out an operation and

[jira] [Updated] (GEODE-697) A client thread timing out an operation and performing further operations can result in cache inconsistency

[ https://issues.apache.org/jira/browse/GEODE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-697: Component/s: (was: client/server) regions > A client thread timing out an

[jira] [Commented] (GEODE-697) A client thread timing out an operation and performing further operations can result in cache inconsistency

[ https://issues.apache.org/jira/browse/GEODE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824466#comment-15824466 ] Udo Kohlmeyer commented on GEODE-697: - I agree with [~hitesh.khamesra] that the most important piece is

Re: Native Client Directory Structure

Jake, Having all the clients in the repository is nice, however, has there been thought to have them in their own repository? Now that we are a TLP, we do have that capability, as seen with the 'geode-examples' repository. --Mark On Mon, Jan 16, 2017 at 10:38 AM, Udo Kohlmeyer

[jira] [Created] (GEODE-2303) Review openssl linking

Anthony Baker created GEODE-2303: Summary: Review openssl linking Key: GEODE-2303 URL: https://issues.apache.org/jira/browse/GEODE-2303 Project: Geode Issue Type: Sub-task

Re: messages repeating when using CQ Query mechanism

And what versions of Geode and GemFire and C++ client are you trying? -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: 631-835-4771 On Mon, Jan 16, 2017 at 1:30 PM, Avital Amity wrote: > Thanks Jason for your comments > > Just to emphasize I'm running

Re: Review Request 55532: GEODE-2198: close and re-create the cache on a server when importing new cluster configuration

> On Jan. 16, 2017, 6:32 p.m., Jared Stewart wrote: > > Ship It! +1 after Kevin's comment is addressed - Jared --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55532/#review161765

Re: Review Request 55532: GEODE-2198: close and re-create the cache on a server when importing new cluster configuration

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55532/#review161765 --- Ship it! Ship It! - Jared Stewart On Jan. 14, 2017, 3:52

RE: messages repeating when using CQ Query mechanism

Thanks Jason for your comments Just to emphasize I'm running the exact same flow once with GEODE and once with GF, and tried it on several environments and go consistent results. I assume it can eliminate network issues These repeating messages are only when using the C++ client (no problem

[jira] [Updated] (GEODE-2299) Integrate Geode with Grafana for historical and real-time metrics analysis

[ https://issues.apache.org/jira/browse/GEODE-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2299: --- Component/s: docs > Integrate Geode with Grafana for historical and real-time metrics

[jira] [Commented] (GEODE-1733) Lucene indexes stats are zeroed after recovering from indexes from disk

[ https://issues.apache.org/jira/browse/GEODE-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824375#comment-15824375 ] ASF subversion and git services commented on GEODE-1733: Commit

[jira] [Created] (GEODE-2301) Deprecate JTA transaction manager from Geode

Swapnil Bawaskar created GEODE-2301: --- Summary: Deprecate JTA transaction manager from Geode Key: GEODE-2301 URL: https://issues.apache.org/jira/browse/GEODE-2301 Project: Geode Issue Type:

[jira] [Commented] (GEODE-2272) Pulse Data Browser export hangs

[ https://issues.apache.org/jira/browse/GEODE-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824355#comment-15824355 ] ASF GitHub Bot commented on GEODE-2272: --- GitHub user jaredjstewart opened a pull request:

[jira] [Updated] (GEODE-2300) Document default names for start locator/server

[ https://issues.apache.org/jira/browse/GEODE-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-2300: --- Issue Type: Sub-task (was: Task) Parent: GEODE-182 > Document default names for

[GitHub] geode pull request #338: GEODE-2272: Fix Pulse data browser export

GitHub user jaredjstewart opened a pull request: https://github.com/apache/geode/pull/338 GEODE-2272: Fix Pulse data browser export * Pulse no longer loads all results into the browser before generating a results file for download. You can merge this pull request into a Git

[jira] [Created] (GEODE-2300) Document default names for start locator/server

Joey McAllister created GEODE-2300: -- Summary: Document default names for start locator/server Key: GEODE-2300 URL: https://issues.apache.org/jira/browse/GEODE-2300 Project: Geode Issue

[jira] [Resolved] (GEODE-2194) Initial, post-login Pulse page is /pulse/pulse/pulseVersion

[ https://issues.apache.org/jira/browse/GEODE-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jared Stewart resolved GEODE-2194. -- Resolution: Fixed > Initial, post-login Pulse page is /pulse/pulse/pulseVersion >

[jira] [Updated] (GEODE-2194) Initial, post-login Pulse page is /pulse/pulse/pulseVersion

[ https://issues.apache.org/jira/browse/GEODE-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jared Stewart updated GEODE-2194: - Fix Version/s: 1.1.0 > Initial, post-login Pulse page is /pulse/pulse/pulseVersion >

[jira] [Resolved] (GEODE-1114) Remove sqlfire/GemFireXD references from Pulse

[ https://issues.apache.org/jira/browse/GEODE-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jared Stewart resolved GEODE-1114. -- Resolution: Fixed > Remove sqlfire/GemFireXD references from Pulse >

[jira] [Updated] (GEODE-1114) Remove sqlfire/GemFireXD references from Pulse

[ https://issues.apache.org/jira/browse/GEODE-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jared Stewart updated GEODE-1114: - Fix Version/s: 1.1.0 > Remove sqlfire/GemFireXD references from Pulse >

Re: Native Client Directory Structure

I was initially confused by using the term Native Client for our .NET and C++ clients. If I'm a newcomer to GemFire, is it not more confusing to use the term Native? I vote for switching our terminology to just GemFire + Clients, where the clients can currently be written in Java, .NET, or C++.

Re: Native Client Directory Structure

Udo, Not sure what part of my email you are +1ing. -Jake On Mon, Jan 16, 2017 at 8:45 AM Jacob Barrett wrote: > On Mon, Jan 16, 2017 at 8:35 AM Michael William Dodge > wrote: > > Given that the current source structure uses cpp and cli prefixes for

Re: Native Client Directory Structure

I'm not an expert at .NET development so please bear with me. In that world, is CLI synonymous with C#? It seems that people who want a non-Java client for Geode would be thinking of it in terms of programming language, which is why I suggested csharp. It seems like people writing Geode clients

Re: Native Client Directory Structure

On Mon, Jan 16, 2017 at 8:35 AM Michael William Dodge wrote: > Given that the current source structure uses cpp and cli prefixes for the > C++ and .NET clients, respectively, what about using cpp and cli for the > directories, allowing any new .NET development to go into a

Re: Native Client Directory Structure

Given that the current source structure uses cpp and cli prefixes for the C++ and .NET clients, respectively, what about using cpp and cli for the directories, allowing any new .NET development to go into a separate directory (perhaps cs or csharp) without any additional moves? Sarge > On 16

  1   2   >