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

Christian Tzolov created GEODE-2299: --- Summary: Integrate Geode with Grafana for historical and real-time metrics analysis Key: GEODE-2299 URL: https://issues.apache.org/jira/browse/GEODE-2299 Projec

Re: Visualize Geode Metrics/Stats with Grafana Dashboards

Here is the JIRA ticket: https://issues.apache.org/jira/browse/GEODE-2299 My proposal is to start with something close to what we have prototyped so far: Geode JMX/Statistics -> InfluxDB Time-Series DB -> Grafana with some pre-defined dashboards Next we can enhance it with: 1. Geode Grafana dataso

Build failed in Jenkins: Geode-nightly #718

See -- [...truncated 552 lines...] :geode-json:compileTestJava UP-TO-DATE :geode-json:processTestResources UP-TO-DATE :geode-json:testClasses UP-TO-DATE :geode-json:checkMissedTests UP-TO-DATE :geode-json:sp

Native Client Directory Structure

One of the first things necessary to get NC merged into the the develop branch is understanding where it will go under the current geode project structure. The quick and obvious solution is adding a 'geode-nativeclient` subproject and relocating all the NC sources into that directory. Given that

Re: Native Client Directory Structure

+1 Makes sense to me -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: 631-835-4771 On Mon, Jan 16, 2017 at 11:26 AM, Jacob Barrett wrote: > One of the first things necessary to get NC merged into the the develop > branch is understanding where it will go under the current geode

messages repeating when using CQ Query mechanism

Hi, When using CQQuery mechanism, when moving from GEMFIRE to GEODE we see differences in server log files including many of the following messages: [info ...] Entry expiry tasks disabled because the queue became primary. Old messageTimeToLive was: 180 [fine ...] Started closing CQ CqName: ...

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 J

Re: Native Client Directory Structure

+1 There are discussions relating to the pure Java client. I think it would fight right into the "geode-client" project. --Udo On 1/16/17 08:26, Jacob Barrett wrote: One of the first things necessary to get NC merged into the the develop branch is understanding where it will go under the cu

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 separate > directory (p

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

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 the > C++ and .NET clients, respectively, w

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/#review161751 --- Wouldn't you want all of your lock/release calls to be in a try/fi

Re: Native Client Directory Structure

Let's try this again. Using the +1 mechanism for a multipart email is tough so please include a comment on which part you are +1ing. Also, I want to revise my suggestion to just call the directory 'geode-native' rather than 'geode-nativeclient'. Simply because I am lazy and don't want to type the

Re: Native Client Directory Structure

.NET libraries can be written in any language that supports compilation to CLI. This includes C++/CLI, C#, F#, etc. [1]. Your project need not be written in the same language as the library. This is why I would suggest we not name the client library after the language we used to write it. [1] http

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++. Wh

[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 > --

[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] [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] [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 Type:

[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 start

[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 reposit

[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&focusedCommentId=15824355#comment-15824355 ] ASF GitHub Bot commented on GEODE-2272: --- GitHub user jaredjstewart opened a pull req

Re: messages repeating when using CQ Query mechanism

Hello, I am not sure what would cause that to happen. Just some questions and ideas, it looks like the first log about disabling expiry is logged when we create the ha region queue, become a primary queue or start/restop (and only if the old time to live is > 0. After being the log, it should be

[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-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&focusedCommentId=15824375#comment-15824375 ] ASF subversion and git services commented on GEODE-1733: Commit f1

Re: Review Request 55440: GEODE-1733: Index repository is now created when the chunk bucket becomes primary.

> On Jan. 12, 2017, 8:41 p.m., Dan Smith wrote: > > geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/LuceneIndexForPartitionedRegion.java, > > line 136 > > > > > > nitpick - this could just be passi

[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] [Created] (GEODE-2302) Need ability to plug-in JNDI name of JTATransactionManager

Swapnil Bawaskar created GEODE-2302: --- Summary: Need ability to plug-in JNDI name of JTATransactionManager Key: GEODE-2302 URL: https://issues.apache.org/jira/browse/GEODE-2302 Project: Geode

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 with

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 a.m

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: 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 the exact same flow once w

Re: Native Client Directory Structure

-1 "geode-native" directory name +1 "geode-client" directory name Maybe the directories for the different clients are by language, so we omit the "geode" prefix i.e geode-client/ c++, net java python If clients are in their own project, then the clients can be independen

[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 Reporte

Re: [ANNOUNCE] Donation of improved GemFire native client

> On Jan 15, 2017, at 2:24 AM, Avinash Dongre wrote: > > This is great. > > Need to make following change to PASS the build. > > > diff --git a/src/tests/javaobject/CMakeLists.txt > b/src/tests/javaobject/CMakeLists.txt > index 4924e5c..7f85878 100644 > --- a/src/tests/javaobject/CMakeLists.t

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/ --- (Updated Jan. 16, 2017, 7:14 p.m.) Review request for geode, Barry Oglesby, Jas

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 wrote: > -1 "geo

Re: Native Client Directory Structure

I would love a separate repo. Someone told me that wasn't an option. If it's an option the let's make it so. On Mon, Jan 16, 2017 at 11:20 AM Mark Bretl wrote: > Jake, > > Having all the clients in the repository is nice, however, has there been > thought to have them in their own repository? No

[jira] [Created] (GEODE-2304) Client operation timeouts should be honored by the server instead of the client

Udo Kohlmeyer created GEODE-2304: Summary: Client operation timeouts should be honored by the server instead of the client Key: GEODE-2304 URL: https://issues.apache.org/jira/browse/GEODE-2304 Project

[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&focusedCommentId=15824466#comment-15824466 ] Udo Kohlmeyer commented on GEODE-697: - I agree with [~hitesh.khamesra] that the most im

[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 operat

[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 per

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/ Thank

[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") > ---

[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&focusedCommentId=15824477#comment-15824477 ] Anthony Baker commented on GEODE-2264: -- Based on the discussion from dev@geode this i

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.,

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/ --- (Updated Jan. 16, 2017, 7:37 p.m.) Review request for geode, Barry Oglesby, Jas

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

> On Jan. 12, 2017, 5:26 p.m., Dan Smith wrote: > > I'd say actually get rid of the distributed member id part and just keep > > the name. > > > > Also, I don't think it's good practice to look up a singleton inside the > > constructor for LuceneIndexDetails. It would be better just pass the s

Re: [ANNOUNCE] Donation of improved GemFire native client

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 build the native clients? Both those scenarios don't sound great to me. As a developer

Re: Native Client Directory Structure

I’m cautiously in favor of this idea. Allowing independent parts (geode, geode-examples, geode-native) to progress and release at their own pace seems like a good thing. From a release perspective, I think each repo would have separate vote threads and a section on our release page: http://ge

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

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 joeymcallister commented on a diff in the pull request: > > https://github.com/apache/geode/pull/334#discussion_r95706396 > > --- Diff: geode-book/README.md ---

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

[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 i

[GitHub] geode issue #337: [GEODE-2295] Add constructors for LocatorCancelException

Github user galen-pivotal commented on the issue: https://github.com/apache/geode/pull/337 Moving to review board. --- 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 wis

[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&focusedCommentId=15824519#comment-15824519 ] ASF GitHub Bot commented on GEODE-2295: --- Github user galen-pivotal closed the pull r

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 build the > native clie

[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&focusedCommentId=15824518#comment-15824518 ] ASF GitHub Bot commented on GEODE-2295: --- Github user galen-pivotal commented on the

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

Re: Native Client Directory Structure

+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 would merit have a separate repo for each platform's client, e.g., a repo for the Java client, a repo for the C# client, etc. My instinct is to divide th

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 would > merit have a s

Re: Native Client Directory Structure

+1 to separate client repos. Or at least some ability to independently version client code for releases. --Udo On 1/16/17 11:56, Jacob Barrett wrote: +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

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 joeymcallister commented on a diff in the pull

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 Ko

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 ".NET client" compone

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

Jacob S. Barrett created GEODE-2306: --- Summary: Update native client BUILDING.md to reflect changes for Geode Key: GEODE-2306 URL: https://issues.apache.org/jira/browse/GEODE-2306 Project: Geode

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

Jacob S. Barrett created GEODE-2305: --- Summary: Remove native client packaging dependency on Pivotal EULA Key: GEODE-2305 URL: https://issues.apache.org/jira/browse/GEODE-2305 Project: Geode

[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

[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 ] Jacob S. Barrett updated GEODE-2307: Description: Native client build has dependencies on the Geode product installation. FindGeo

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-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 Type:

[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

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 cove

[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 > -

[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-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] [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] [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&focusedCommentId=15824583#comment-15824583 ] ASF subversion and git services commented on GEODE-2305: Commit 7a

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 > build it as its own User Gu

[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: 1.1.0

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 > wrote: > > > +1 to the se

[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 i

[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 feature

[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&focusedCommentId=15824612#comment-15824612 ] ASF GitHub Bot commented on GEODE-2272: --- Github user jaredjstewart closed the pull r

[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&focusedCommentId=15824611#comment-15824611 ] ASF GitHub Bot commented on GEODE-2272: --- Github user jaredjstewart commented on the

[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&focusedCommentId=15824626#comment-15824626 ] ASF subversion and git services commented on GEODE-2297: Commit de

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, Jared

[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 > -

[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 >

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 --- geode-core/src/main/java/org/apache/geode/internal/logging/log4j/

[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. > ---

[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 Ge

[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. >

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 p.m.,

[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

[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 s

[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 reposit

[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&focusedCommentId=15824682#comment-15824682 ] ASF GitHub Bot commented on GEODE-2272: --- Github user jaredjstewart commented on the

[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&focusedCommentId=15824681#comment-15824681 ] ASF GitHub Bot commented on GEODE-2272: --- GitHub user jaredjstewart opened a pull req

[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 automatica

  1   2   >