[jira] [Commented] (GEODE-2605) Unable to do a Lucene query without CLUSTER:READ privilege

[ https://issues.apache.org/jira/browse/GEODE-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898640#comment-15898640 ] Diane Hardman commented on GEODE-2605: -- When I add CLUSTER:READ to my dataAdmin user (which already

[jira] [Created] (GEODE-2605) Unable to do a Lucene query without CLUSTER:READ privilege

Diane Hardman created GEODE-2605: Summary: Unable to do a Lucene query without CLUSTER:READ privilege Key: GEODE-2605 URL: https://issues.apache.org/jira/browse/GEODE-2605 Project: Geode

[jira] [Assigned] (GEODE-2525) Replace random number implementation with C++11 standards

[ https://issues.apache.org/jira/browse/GEODE-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett reassigned GEODE-2525: --- Assignee: Jacob S. Barrett > Replace random number implementation with C++11

[jira] [Updated] (GEODE-2525) Replace random number implementation with C++11 standards

[ https://issues.apache.org/jira/browse/GEODE-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett updated GEODE-2525: Issue Type: Task (was: Bug) > Replace random number implementation with C++11 standards >

[jira] [Commented] (GEODE-2509) Build failed at openSUSE LEAP 42.2

[ https://issues.apache.org/jira/browse/GEODE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898589#comment-15898589 ] Jacob S. Barrett commented on GEODE-2509: - Rather than attaching a patch would you be willing to

[jira] [Assigned] (GEODE-2493) Replace the locking and CAS operations provided in HostAsm with C++11 standards

[ https://issues.apache.org/jira/browse/GEODE-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett reassigned GEODE-2493: --- Assignee: Jacob S. Barrett > Replace the locking and CAS operations provided in

[jira] [Resolved] (GEODE-2317) native client cmake build should honor GEODE_HOME environment variable

[ https://issues.apache.org/jira/browse/GEODE-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett resolved GEODE-2317. - Resolution: Fixed > native client cmake build should honor GEODE_HOME environment

[jira] [Resolved] (GEODE-2604) Add javadocs comments to LuceneIndexMetrics

[ https://issues.apache.org/jira/browse/GEODE-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun resolved GEODE-2604. Resolution: Fixed Fix Version/s: 1.2.0 > Add javadocs comments to LuceneIndexMetrics >

[jira] [Commented] (GEODE-2602) Resolve C++11 and minimum support compilers discrepancies

[ https://issues.apache.org/jira/browse/GEODE-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898574#comment-15898574 ] Jacob S. Barrett commented on GEODE-2602: - feature/GEODE-2602 rolls up the attached blocked

[jira] [Commented] (GEODE-2552) Replace NanoTimer with std::chrono / std::this_thread::sleep_for

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

[jira] [Commented] (GEODE-2604) Add javadocs comments to LuceneIndexMetrics

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

[jira] [Commented] (GEODE-2494) Replace SpinLock class with C++11 style BasicLockable class, spinlock_mutex.

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

[jira] [Commented] (GEODE-2494) Replace SpinLock class with C++11 style BasicLockable class, spinlock_mutex.

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

[jira] [Commented] (GEODE-2604) Add javadocs comments to LuceneIndexMetrics

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

[jira] [Commented] (GEODE-2552) Replace NanoTimer with std::chrono / std::this_thread::sleep_for

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

[jira] [Commented] (GEODE-2494) Replace SpinLock class with C++11 style BasicLockable class, spinlock_mutex.

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

[jira] [Commented] (GEODE-2494) Replace SpinLock class with C++11 style BasicLockable class, spinlock_mutex.

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

[jira] [Commented] (GEODE-2531) Replace HostAsm::atomic* and AtomicInc with std::atomic

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

[jira] [Commented] (GEODE-2494) Replace SpinLock class with C++11 style BasicLockable class, spinlock_mutex.

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

[jira] [Commented] (GEODE-2552) Replace NanoTimer with std::chrono / std::this_thread::sleep_for

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

[jira] [Commented] (GEODE-2604) Add javadocs comments to LuceneIndexMetrics

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

[jira] [Commented] (GEODE-2513) Geode Native docs: rebrand to match open-source software

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

[jira] [Updated] (GEODE-2602) Resolve C++11 and minimum support compilers discrepancies

[ https://issues.apache.org/jira/browse/GEODE-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett updated GEODE-2602: Description: Referencing BUILDING.md our target language is C++11 and we state: {noformat}

[jira] [Commented] (GEODE-2604) Add javadocs comments to LuceneIndexMetrics

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

[GitHub] geode pull request #415: GEODE-2604: Added javadoc comments to LuceneIndexMe...

GitHub user nabarunnag opened a pull request: https://github.com/apache/geode/pull/415 GEODE-2604: Added javadoc comments to LuceneIndexMetrics.java @upthewaterspout @jhuynh1 @gesterzhou @boglesby @ladyVader You can merge this pull request into a Git repository by running: $

[jira] [Resolved] (GEODE-2596) Moving LuceneIndexMetrics and LuceneServiceMXBean to public API

[ https://issues.apache.org/jira/browse/GEODE-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun resolved GEODE-2596. Resolution: Fixed Fix Version/s: 1.2.0 > Moving LuceneIndexMetrics and LuceneServiceMXBean to public

[jira] [Commented] (GEODE-2596) Moving LuceneIndexMetrics and LuceneServiceMXBean to public API

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

[jira] [Commented] (GEODE-2596) Moving LuceneIndexMetrics and LuceneServiceMXBean to public API

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

[GitHub] geode pull request #414: GEODE-2596: Lucene metrics moved to public API

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

[jira] [Created] (GEODE-2604) Add javadocs comments to LuceneIndexMetrics

nabarun created GEODE-2604: -- Summary: Add javadocs comments to LuceneIndexMetrics Key: GEODE-2604 URL: https://issues.apache.org/jira/browse/GEODE-2604 Project: Geode Issue Type: Bug

Re: Building geode-native for release

> On Mar 6, 2017, at 10:29 AM, Jacob Barrett wrote: > > On Mon, Mar 6, 2017 at 9:56 AM Anthony Baker wrote: > > - The distributions don’t include the version in the top-level directory. > We should include that. > > I believe you are looking for `make

[GitHub] geode-native pull request #46: GEODE-2603 Docs: geode-native user guide >> S...

GitHub user davebarnes97 opened a pull request: https://github.com/apache/geode-native/pull/46 GEODE-2603 Docs: geode-native user guide >> Security >> SSL setup nee… …ds update You can merge this pull request into a Git repository by running: $ git pull

Re: Building geode-native for release

I believe there are some differences between these schemas (not to say that we should fix that over time). Anthony > On Mar 6, 2017, at 11:46 AM, Michael William Dodge wrote: > > Can we not just use http://geode.apache.org/schema/cache/cache-1.0.xsd >

[jira] [Commented] (GEODE-2539) Upgrading Jetty causes RestSecurityIntegrationTest to fail

[ https://issues.apache.org/jira/browse/GEODE-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898395#comment-15898395 ] Kevin Duling commented on GEODE-2539: - Upgrading to 9.4.2.v20170220 causes an assertion failure

[jira] [Created] (GEODE-2603) Docs: geode-native user guide >> Security >> SSL setup needs update

Dave Barnes created GEODE-2603: -- Summary: Docs: geode-native user guide >> Security >> SSL setup needs update Key: GEODE-2603 URL: https://issues.apache.org/jira/browse/GEODE-2603 Project: Geode

[jira] [Assigned] (GEODE-2603) Docs: geode-native user guide >> Security >> SSL setup needs update

[ https://issues.apache.org/jira/browse/GEODE-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2603: -- Assignee: Dave Barnes > Docs: geode-native user guide >> Security >> SSL setup needs update >

[jira] [Assigned] (GEODE-2539) Upgrading Jetty causes RestSecurityIntegrationTest to fail

[ https://issues.apache.org/jira/browse/GEODE-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-2539: --- Assignee: Kevin Duling > Upgrading Jetty causes RestSecurityIntegrationTest to fail >

[jira] [Assigned] (GEODE-2552) Replace NanoTimer with std::chrono / std::this_thread::sleep_for

[ https://issues.apache.org/jira/browse/GEODE-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett reassigned GEODE-2552: --- Assignee: Jacob S. Barrett > Replace NanoTimer with std::chrono /

[jira] [Updated] (GEODE-2602) Resolve C++11 and minimum support compilers discrepancies

[ https://issues.apache.org/jira/browse/GEODE-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett updated GEODE-2602: Description: Referencing BUILDING.md our target language is C++11 and we state: {noformat}

[jira] [Created] (GEODE-2602) Resolve C++11 and minimum support compilers discrepancies

Jacob S. Barrett created GEODE-2602: --- Summary: Resolve C++11 and minimum support compilers discrepancies Key: GEODE-2602 URL: https://issues.apache.org/jira/browse/GEODE-2602 Project: Geode

Re: [GitHub] geode pull request #404: Geode 2469

And correcting the spelling of "SEPERATOR" would be a plus while changing the code. *Wes Williams | Pivotal Advisory **Data Engineer* 781.606.0325 http://pivotal.io/big-data/pivotal-gemfire On Mon, Mar 6, 2017 at 6:14 PM, galen-pivotal wrote: > Github user galen-pivotal

[jira] [Created] (GEODE-2601) Banner is logged twice during locator startup

Patrick Rhomberg created GEODE-2601: --- Summary: Banner is logged twice during locator startup Key: GEODE-2601 URL: https://issues.apache.org/jira/browse/GEODE-2601 Project: Geode Issue

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #492 was SUCCESSFUL (with 1680 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #492 was successful. --- Scheduled 1682 tests in total. https://build.spring.io/browse/SGF-NAG-492/ -- This

[jira] [Updated] (GEODE-2600) Inconsistent spacing of headers in Startup Configuration log

[ https://issues.apache.org/jira/browse/GEODE-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg updated GEODE-2600: Affects Version/s: 1.2.0 > Inconsistent spacing of headers in Startup Configuration log >

[jira] [Created] (GEODE-2600) Inconsistent spacing of headers in Startup Configuration log

Patrick Rhomberg created GEODE-2600: --- Summary: Inconsistent spacing of headers in Startup Configuration log Key: GEODE-2600 URL: https://issues.apache.org/jira/browse/GEODE-2600 Project: Geode

[jira] [Updated] (GEODE-2599) `start locator` prints `null` in startup dots.

[ https://issues.apache.org/jira/browse/GEODE-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg updated GEODE-2599: Affects Version/s: 1.2.0 > `start locator` prints `null` in startup dots. >

[jira] [Created] (GEODE-2599) `start locator` prints `null` in startup dots.

Patrick Rhomberg created GEODE-2599: --- Summary: `start locator` prints `null` in startup dots. Key: GEODE-2599 URL: https://issues.apache.org/jira/browse/GEODE-2599 Project: Geode Issue

[jira] [Commented] (GEODE-2488) Netstat command fails with OutOfMemoryError

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

[jira] [Commented] (GEODE-2578) Query string limited to 64 KiB

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

[GitHub] geode-native issue #44: GEODE-2578: Remove 64 KiB limit on query strings.

Github user PivotalSarge commented on the issue: https://github.com/apache/geode-native/pull/44 The unit tests failed on Linux but not other platforms. It turns out that DataOutput has some not-very-obvious (and apparently platform-specific) behavior around buffer management that

[jira] [Created] (GEODE-2598) Verify buffer allocation behavior of apache::geode::client::DataOutput

Michael Dodge created GEODE-2598: Summary: Verify buffer allocation behavior of apache::geode::client::DataOutput Key: GEODE-2598 URL: https://issues.apache.org/jira/browse/GEODE-2598 Project: Geode

Re: Building geode-native for release

That is for the java client. It would be nice if they were the same plus some platform specific namespaces extensions. Sadly that isn't the case... yet. On Mon, Mar 6, 2017 at 11:54 AM Michael William Dodge wrote: > Can we not just use

Re: Review Request 57345: GEODE-2579: ClassCastException cannot cast CompiledIn to CompiledJunction when querying with a junction containing an in clause

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57345/#review168034 --- Ship it! Ship It! - Dan Smith On March 6, 2017, 7:38 p.m.,

[jira] [Resolved] (GEODE-2571) CacheClosedException during LuceneQueryFunction should be handled with a retry

[ https://issues.apache.org/jira/browse/GEODE-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh resolved GEODE-2571. Resolution: Fixed Fix Version/s: 1.2.0 > CacheClosedException during LuceneQueryFunction

[jira] [Commented] (GEODE-2596) Moving LuceneIndexMetrics and LuceneServiceMXBean to public API

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

[GitHub] geode pull request #414: GEODE-2596: Lucene metrics moved to public API

GitHub user nabarunnag opened a pull request: https://github.com/apache/geode/pull/414 GEODE-2596: Lucene metrics moved to public API * LuceneIndexMetrics and LuceneServiceMXBean were moved to org.apache.geode.cache.lucene.management -- Lucene precheckin

Re: Building geode-native for release

Can we not just use http://geode.apache.org/schema/cache/cache-1.0.xsd which is already there? Sarge > On 6 Mar, 2017, at 09:56, Anthony Baker wrote: > > 2) Schema > > We need to move gfcpp-cache-9.0.xsd to

Re: Gemfire proxy cache race condition bug?

This is a known limitation of CacheListeners on a PROXY region. On other types of regions the local region entry that the operation is modifying is synchronized during the operation and during the CacheListener invocation. That is what the javadocs on the CacheListener calls "holding a lock on the

[jira] [Resolved] (GEODE-2597) Redis adapter doesn't handle UTF-8 properly.

[ https://issues.apache.org/jira/browse/GEODE-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Galen O'Sullivan resolved GEODE-2597. - Resolution: Invalid > Redis adapter doesn't handle UTF-8 properly. >

[jira] [Updated] (GEODE-2597) Redis adapter doesn't handle UTF-8 properly.

[ https://issues.apache.org/jira/browse/GEODE-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Galen O'Sullivan updated GEODE-2597: Description: {code} 127.0.0.1:6379> hset foo å å (integer) 1 (2.09s) 127.0.0.1:6379> hget

[jira] [Created] (GEODE-2597) Redis adapter doesn't handle UTF-8 properly.

Galen O'Sullivan created GEODE-2597: --- Summary: Redis adapter doesn't handle UTF-8 properly. Key: GEODE-2597 URL: https://issues.apache.org/jira/browse/GEODE-2597 Project: Geode Issue Type:

Review Request 57345: GEODE-2579: ClassCastException cannot cast CompiledIn to CompiledJunction when querying with a junction containing an in clause

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57345/ --- Review request for geode, nabarun nag and Dan Smith. Bugs: GEODE-2579

[jira] [Assigned] (GEODE-2596) Moving LuceneIndexMetrics and LuceneServiceMXBean to public API

[ https://issues.apache.org/jira/browse/GEODE-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun reassigned GEODE-2596: -- Assignee: nabarun > Moving LuceneIndexMetrics and LuceneServiceMXBean to public API >

[jira] [Created] (GEODE-2596) Moving LuceneIndexMetrics and LuceneServiceMXBean to public API

nabarun created GEODE-2596: -- Summary: Moving LuceneIndexMetrics and LuceneServiceMXBean to public API Key: GEODE-2596 URL: https://issues.apache.org/jira/browse/GEODE-2596 Project: Geode Issue

[jira] [Updated] (GEODE-2595) Change LuceneService.createIndex to use a factory pattern

[ https://issues.apache.org/jira/browse/GEODE-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-2595: - Issue Type: Improvement (was: Bug) > Change LuceneService.createIndex to use a factory pattern >

[jira] [Created] (GEODE-2595) Change LuceneService.createIndex to use a factory pattern

Dan Smith created GEODE-2595: Summary: Change LuceneService.createIndex to use a factory pattern Key: GEODE-2595 URL: https://issues.apache.org/jira/browse/GEODE-2595 Project: Geode Issue Type:

[jira] [Resolved] (GEODE-2588) OQL's ORDER BY takes 13x (1300%) more time compared to plain java sort for the same amount of data and same resources

[ https://issues.apache.org/jira/browse/GEODE-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun resolved GEODE-2588. Resolution: Duplicate > OQL's ORDER BY takes 13x (1300%) more time compared to plain java sort for > the

Re: Export Control for Geode

Thanks Mark! Let me know if you have any questions. Anthony > On Mar 6, 2017, at 10:32 AM, Mark Bretl wrote: > > Looks good. Unless there are any other comments/issues, I will start this > tomorrow. > > --Mark > > On Thu, Mar 2, 2017 at 10:29 PM, Anthony Baker

Re: Export Control for Geode

Looks good. Unless there are any other comments/issues, I will start this tomorrow. --Mark On Thu, Mar 2, 2017 at 10:29 PM, Anthony Baker wrote: > After reviewing [1], I think we need to record and report our use of > cryptographic libraries that fall under US export

Re: Building geode-native for release

On Mon, Mar 6, 2017 at 9:56 AM Anthony Baker wrote: GEODE-1416 lays out the tasks needed to prepare geode-native to be included in a geode release. I spent some time reviewing the source and found several other things to consider: 3) Build The cmake build can produce source

[jira] [Updated] (GEODE-2594) Remove optional usage of Attach API

[ https://issues.apache.org/jira/browse/GEODE-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2594: - Labels: gfsh (was: ) > Remove optional usage of Attach API > --- > >

[jira] [Created] (GEODE-2594) Remove optional usage of Attach API

Kirk Lund created GEODE-2594: Summary: Remove optional usage of Attach API Key: GEODE-2594 URL: https://issues.apache.org/jira/browse/GEODE-2594 Project: Geode Issue Type: Improvement

Re: Review Request 57342: GEODE-2267: mark local time sensitive tests as flaky

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57342/#review168015 --- Ship it! Ship It! - Kirk Lund On March 6, 2017, 5:03 p.m.,

[jira] [Commented] (GEODE-2267) Add gfsh command to export stat files

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

Re: ACE version for C++ client (not grant)

Geode Native will be release with Geode in the future. It has never been release with Geode using ACE 6.3.3. On Mon, Mar 6, 2017 at 8:27 AM Avital Amity wrote: > Well We took it when it was compiled with ACE 6.3.3 > C++ client isn't an official part of GEODE? It is a

Review Request 57342: GEODE-2267: mark local time sensitive tests as flaky

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57342/ --- Review request for geode. Repository: geode Description --- GEODE-2267:

Re: Gemfire proxy cache race condition bug?

If you always do whatever processing you are planning to do inside the CacheListener and use the "newValue" field that is supplied to that callback you will always begin processing in the order the data was received. I suppose if you want to ensure that you are completing processing in the correct

Re: ACE version for C++ client (not grant)

We’re continuing to work on several improvements needed to meet ASF and Geode release standards. This work is being tracked on GEODE-1416 (see https://issues.apache.org/jira/browse/GEODE-1416 ). I plan to send out an update later today. And

Re: Review Request 57311: GEODE-2593: add port range to AvailablePortHelper to fix testUDPPortRange

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

Build failed in Jenkins: Geode-nightly #768

See -- [...truncated 100.05 KB...] org.apache.geode.management.internal.cli.commands.ExportLogsDUnitTest > testExportWithStartAndEndDateTimeFiltering FAILED java.lang.AssertionError:

Re: ACE version for C++ client (not grant)

Avital, If by "grant" you mean the 'next-gen-native-client-software-grant’ branch then you are in the wrong repo. You will want to use: https://github.com/apache/geode-native Geode Native will be included in a future release of Geode, but you are welcome to use what is there currently. Best,

RE: ACE version for C++ client (not grant)

Well We took it when it was compiled with ACE 6.3.3 C++ client isn't an official part of GEODE? It is a mandatory part for us. Thanks Avital -Original Message- From: Jacob Barrett [mailto:jbarr...@pivotal.io] Sent: Monday, March 06, 2017 6:12 PM To: dev@geode.apache.org Subject: Re: ACE

Re: [GitHub] geode-native issue #44: GEODE-2578: Remove 64 KiB limit on query strings.

They didn't for me before I committed the code. Let me try them again. > On 6 Mar, 2017, at 08:03, pivotal-jbarrett wrote: > > Github user pivotal-jbarrett commented on the issue: > >https://github.com/apache/geode-native/pull/44 > >@PivotalSarge looks like some

Re: ACE version for C++ client (not grant)

There was no previous release of Geode Native. In fact there have not been any releases of Geode Native. On Mon, Mar 6, 2017 at 8:07 AM Avital Amity wrote: > This is on the grant, I have the previous version, there in this file I > can see it's 6.3.3... > Anyway I will

[GitHub] geode-native issue #44: GEODE-2578: Remove 64 KiB limit on query strings.

Github user pivotal-jbarrett commented on the issue: https://github.com/apache/geode-native/pull/44 @PivotalSarge looks like some unit tests are failing. --- 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

[jira] [Commented] (GEODE-2578) Query string limited to 64 KiB

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

RE: ACE version for C++ client (not grant)

This is on the grant, I have the previous version, there in this file I can see it's 6.3.3... Anyway I will check the flags there Thanks Avital -Original Message- From: Jacob Barrett [mailto:jbarr...@pivotal.io] Sent: Monday, March 06, 2017 6:00 PM To: dev@geode.apache.org

Re: ACE version for C++ client (not grant)

Geode is not compiling against ACE 6.3.3. It is currently compiling against ACE 6.4.1. The src/dependencies/ACE/CMakeLists.text project will show you all the flags used to compile the ACE library. The library is statically linked to Geode to produce the Geode dynamic library. -Jake On Mon, Mar

Re: Feature branch cleanup

Last chance to comment: I’ll be cleaning up these branches over the next few days. Anthony > On Feb 27, 2017, at 8:58 AM, Dan Smith wrote: > > +1 > > -Dan > > On Fri, Feb 24, 2017 at 10:35 PM, Anthony Baker wrote: > >> >> The following 100+ feature

Re: Review Request 57311: GEODE-2593: add port range to AvailablePortHelper to fix testUDPPortRange

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57311/#review167987 --- Ship it! Ship It! - Kevin Duling On March 3, 2017, 5:57

[GSoC] Interested in GSoC 2017 ideas

Hi All, I am Kai, a master student majoring in CS from Portland State University, highly interested in Big data and Distributed System. I have contributed to Apache Spark as a GSoC project last year. I've been contributing to Geode codebase. Some my Pull Requests are here.(

[jira] [Commented] (GEODE-1702) Release transaction lock before calling AsyncEventListener

[ https://issues.apache.org/jira/browse/GEODE-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897512#comment-15897512 ] Christian Tzolov commented on GEODE-1702: - [~amb] AFAIK this behavior is in:

RE: ACE version for C++ client (not grant)

Yes, it is 6.3.3 - but is the product (ACE dll) part of the GEODE? How can I know its compilation flags? -Original Message- From: Jacob Barrett [mailto:jbarr...@pivotal.io] Sent: Monday, March 06, 2017 4:07 PM To: dev@geode.apache.org Subject: Re: ACE version for C++ client (not grant)

Re: ACE version for C++ client (not grant)

The version used in Geode is compiled using the dependency CMake files. See src/dependencies/ACE. On Mon, Mar 6, 2017 at 5:22 AM Avital Amity wrote: > Hi, > > We are currently using GEODE C++ client (not grant version) > I see it was compiled with ACE 6.3.3 - anyone

ACE version for C++ client (not grant)

Hi, We are currently using GEODE C++ client (not grant version) I see it was compiled with ACE 6.3.3 - anyone knows if the specific ACE that was used is part of the GEODE sources How can I get the specific lib it was compiled with (for Windows) Thanks Avital This message and the

[GitHub] geode pull request #404: Geode 2469

Github user ggreen commented on a diff in the pull request: https://github.com/apache/geode/pull/404#discussion_r104402728 --- Diff: geode-core/src/main/java/org/apache/geode/redis/internal/executor/hash/HashInterpreter.java --- @@ -0,0 +1,126 @@ +/* + * Licensed to the