I think if you embed the sessionId into your value object and create an
index, that should perform better. I am assuming if you embed the sesionId
that you would then be doing queries more similar to sessionId = X or
sessionId like sessionId%. Being able to use the index will prevent the
query
---
Spring Data GemFire > Nightly-ApacheGeode > #1057 was successful.
---
Scheduled
2458 tests in total.
https://build.spring.io/browse/SGF-NAG-1057/
--
+1
- Verified clean build from source
- Built and ran all geode-examples
On Fri, Sep 28, 2018 at 8:52 PM Sai Boorlagadda
wrote:
> +1
>
> * verified signatures
>
> * verified source distribution builds
>
> * ran basic gfsh commands
>
> * started pulse
>
> * verified examples work with rc2
>
>
>
> Patrick, you just mentioned the java-library plugin's ability to
> distinguish between api and implementation dependencies. Geode doesn't use
> that plugin yet AFAIK, nor does the PR introduce that plugin right?
That is correct, we do not yet make use of the `java-library` plugin (which
has the
Hello all.
I've been getting some strange failures lately, with the output given
below. I have noticed that creating a `gradle wrapper` fixes these
issues. However, since the gradle wrapper is part of the git tree, I was
curious to know if anyone else was having this problem.
If so, we
If what we are doing is just making sure that each geode module is
explicitly declaring all of its first order dependencies (things that
directly show up in import statements) in its build.gradle, then this seems
good to me.
I don't think we want to stop using gradle's ability to pull in all of
I think it would be easier to review and discuss these changes with smaller,
more focused PR’s. Is there a way to split up these changes? That would help
me a lot and I would be less concerned about introducing a problem with our
POM’s / dependencies.
Thanks,
Anthony
> On Oct 1, 2018, at
You might be running into this: https://stackoverflow.com/a/52510288
On Mon, Oct 1, 2018 at 2:03 PM Patrick Rhomberg
wrote:
> Hello all.
>
> I've been getting some strange failures lately, with the output given
> below. I have noticed that creating a `gradle wrapper` fixes these
> issues.
Hi,
I still haven't heard back about this. Can I have access? Who grants it? If
not, what are the criteria for inclusion?
Thanks,
Galen
On Thu, Sep 20, 2018 at 10:57 AM Galen O'Sullivan
wrote:
> Hi,
>
> I would like to have admin access to Concourse at
> https://concourse.apachegeode-ci.info/
