On Thu, Aug 13, 2015 at 5:56 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> In this case, since user called getOrCreateCache(), Ignite did not create a
> cache because it already existed and also did not throw an exception
> because method should return existing cache if a cache with
On Thu, Aug 13, 2015 at 10:03 PM, Vladimir Ozerov
wrote:
> May be we can return not only cache instance, but also a boolean defining
> whether a cache was created by this call or not?
> E.g.:
>
> IgniteCache getOrCreateCache(...);
>
> IgniteCache getOrCreateCache(..., CacheCreateResult);
>
> clas
This way you will not know who exactly created the cache. As a result you
cannot be certain whether your call to getOrCreateCache() created a cache
or you just received already existing instance.
On Fri, Aug 14, 2015 at 8:55 AM, Alexey Kuznetsov
wrote:
> Or we could have isCreated() property on
Community,
I would like to ask an engineer who is experienced in cache query
managers and adapter to make a review of my changes:
https://issues.apache.org/jira/browse/IGNITE-1239
Accodring to the GIT change history great candidates are Alexey G,
Valentin and Semen. :)
--
Denis
Or we could have isCreated() property on cache itself.
On Fri, Aug 14, 2015 at 12:03 PM, Vladimir Ozerov
wrote:
> May be we can return not only cache instance, but also a boolean defining
> whether a cache was created by this call or not?
> E.g.:
>
> IgniteCache getOrCreateCache(...);
>
> Ignite
May be we can return not only cache instance, but also a boolean defining
whether a cache was created by this call or not?
E.g.:
IgniteCache getOrCreateCache(...);
IgniteCache getOrCreateCache(..., CacheCreateResult);
class CacheCreateResult {
boolean isCreated();
}
On Fri, Aug 14, 2015 at
On Thu, Aug 13, 2015 at 06:31PM, Dmitriy Setrakyan wrote:
> On Thu, Aug 13, 2015 at 6:14 PM, Konstantin Boudnik wrote:
>
> > Yeah, as I said don't worry about it guys: it isn't the first graduation
> > from
> > the Incubator, not the last, nor most special. INFRA knows what they are
> > doing
> >
I forgot that the mailing list takes out all formatting, the diagram meant
to be in a monospaced font :)
I added it to Ignite wiki:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
2015-08-13 19:22 GMT-07:00 Alexey Goncharuk :
> While the process of a pull-request creation an
While the process of a pull-request creation and CI run is clear for, the
whole cycle from start to end is still fuzzy. Let me summarize my
understanding and correct me if I got something wrong.
For any committer/contributor John Doe we will have the following structure:
++
Valentin Kulichenko created IGNITE-1248:
---
Summary: Add a method to retrieve Spring application context
Key: IGNITE-1248
URL: https://issues.apache.org/jira/browse/IGNITE-1248
Project: Ignite
GitHub user vkulichenko opened a pull request:
https://github.com/apache/incubator-ignite/pull/18
# ignite-1228
Signed-off-by: Valentin Kulichenko
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite ignit
GitHub user vkulichenko opened a pull request:
https://github.com/apache/incubator-ignite/pull/17
# ignite-1205
Signed-off-by: Valentin Kulichenko
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite ignit
On Thu, Aug 13, 2015 at 6:14 PM, Konstantin Boudnik wrote:
> Yeah, as I said don't worry about it guys: it isn't the first graduation
> from
> the Incubator, not the last, nor most special. INFRA knows what they are
> doing
> ;)
>
Haha... I am going to disagree. It is the most special and endear
Yeah, as I said don't worry about it guys: it isn't the first graduation from
the Incubator, not the last, nor most special. INFRA knows what they are doing
;)
On Thu, Aug 13, 2015 at 05:52PM, Dmitriy Setrakyan wrote:
> On Thu, Aug 13, 2015 at 5:47 PM, Alexey Kuznetsov
> wrote:
>
> > But, why I
On Thu, Aug 13, 2015 at 05:54PM, Dmitriy Setrakyan wrote:
> On Thu, Aug 13, 2015 at 5:51 PM, Konstantin Boudnik wrote:
>
> > On Thu, Aug 13, 2015 at 05:40PM, Alexey Goncharuk wrote:
> > > Maybe I miss a good piece of information about how Git works, but I
> > always
> > > thought that if a pull r
Woohoo! The Github integration is operational ;-)
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Fri, Aug 14, 2015
GitHub user raulk opened a pull request:
https://github.com/apache/incubator-ignite/pull/16
IGNITE-1203 Implement Cluster Discovery via Apache ZooKeeper.
Notes:
* You may have conflicts on GridArgumentChecker, if you merge my jms11
module first. Or viceversa.
* Same goe
In this case, since user called getOrCreateCache(), Ignite did not create a
cache because it already existed and also did not throw an exception
because method should return existing cache if a cache with the same name
already exists.
We may want to implement a check to verify that cache configura
On Thu, Aug 13, 2015 at 5:51 PM, Konstantin Boudnik wrote:
> On Thu, Aug 13, 2015 at 05:40PM, Alexey Goncharuk wrote:
> > Maybe I miss a good piece of information about how Git works, but I
> always
> > thought that if a pull request is accepted, it will be merged to the
> GitHub
> > mirror of Ap
On Thu, Aug 13, 2015 at 5:47 PM, Alexey Kuznetsov
wrote:
> But, why I can open both http://ignite.apache.org and
> https://ignite.incubator.apache.org?
>
> It is a part of graduation?
>
I believe that after graduation, the incubator link will redirect to
ignite.apache.org URL.
>
> On Fri, Aug
Aliases are getting created in prep for the board meeting next week. Don't
read too much into it ;)
On Fri, Aug 14, 2015 at 07:47AM, Alexey Kuznetsov wrote:
> But, why I can open both http://ignite.apache.org and
> https://ignite.incubator.apache.org?
>
> It is a part of graduation?
>
> On Fri,
On Thu, Aug 13, 2015 at 05:40PM, Alexey Goncharuk wrote:
> Maybe I miss a good piece of information about how Git works, but I always
> thought that if a pull request is accepted, it will be merged to the GitHub
> mirror of Apache Ignite. How will this change get to the original Apache
> git reposi
But, why I can open both http://ignite.apache.org and
https://ignite.incubator.apache.org?
It is a part of graduation?
On Fri, Aug 14, 2015 at 12:56 AM, Konstantin Boudnik wrote:
> It isn't a graduation related issue ;) This is affecting a number of other
> lists as well, unfortunately.
>
> Cos
Maybe I miss a good piece of information about how Git works, but I always
thought that if a pull request is accepted, it will be merged to the GitHub
mirror of Apache Ignite. How will this change get to the original Apache
git repository?
Can somebody explain to me the merge procedure?
2015-08-1
Sergi Vladykin created IGNITE-1247:
--
Summary: Support @QuerySqlField.Group annotation outside of
@QuerySqlField
Key: IGNITE-1247
URL: https://issues.apache.org/jira/browse/IGNITE-1247
Project: Ignite
On Thu, Aug 13, 2015 at 10:56 AM, Konstantin Boudnik wrote:
> It isn't a graduation related issue ;) This is affecting a number of other
> lists as well, unfortunately.
>
Argh... For a moment there we felt really special :)
>
> Cos
>
> On Thu, Aug 13, 2015 at 07:44AM, Dmitriy Setrakyan wrote:
Github user ashutakGG closed the pull request at:
https://github.com/apache/incubator-ignite/pull/13
---
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 fea
+1
It is hard to understand why do we have so much different annotations for
injections while requierd resource type could be clearly derived from field
or method types. Looks like a single annotation will be enough. And it
should not be hard to abstract out injection logic into SPI.
On Thu, Aug
It isn't a graduation related issue ;) This is affecting a number of other
lists as well, unfortunately.
Cos
On Thu, Aug 13, 2015 at 07:44AM, Dmitriy Setrakyan wrote:
> Hi,
>
> As many of you have noticed, we are having mailing list problems. Some
> emails arrive late, while others don't arrive
kcheng.mvp created IGNITE-1246:
--
Summary: Exception in thread "main" javax.cache.CacheException:
class org.apache.ignite.IgniteCheckedException: Failed to validate cache
configuration. Cache store factory is not serializable. Cache name: XXX
Hello,
Long story short, I'd love to be able to intercept the resource injection
calls.
For example, in our application we do not use Spring, and also, we do not
expect the developers to use Ignite-specific annotations in the application
code. Instead, we use the standard javax.inject API's @
Hi,
As many of you have noticed, we are having mailing list problems. Some
emails arrive late, while others don't arrive at all.
I believe that it is caused by the Ignite graduation, and INFRA is trying
to switch all emails to the TLP format. An INFRA issue was filed:
https://issues.apache.org/ji
After more thinking about ordering on backups instead of
thread-per-partition I believe this approach won't work.
First it is possible that primary executes for some key , (from different threads), then crashes and only message is
sent to backup, so backup won't be able to restore correct orderi
In the current test framework the easiest way to start multiple instances
would be to call startGrids(cnt) and override the method
getConfiguration(String). This method in GridCommonAbstractTest does some
optimizations that make tests run faster and prepares a default
configuration, so all you need
Semen Boikov created IGNITE-1245:
Summary: Continuous query listeners created by clients are not
registered on joining nodes
Key: IGNITE-1245
URL: https://issues.apache.org/jira/browse/IGNITE-1245
Pro
In the current test framework the easiest way to start multiple instances
would be to call startGrids(cnt) and override the method
getConfiguration(String). This method in GridCommonAbstractTest does some
optimizations that make tests run faster and prepares a default
configuration, so all you need
Why "reply-to" is dev@ignite.incubator.apache.org? Cos? Brane? Any ideas?
--Yakov
2015-08-13 9:20 GMT+03:00 Dmitriy Setrakyan :
> Test.
>
> D.
>
37 matches
Mail list logo
