Malcolm,
I added you to contributors.
On Sat, Jul 22, 2017 at 1:15 PM, Malcolm Taylor wrote:
> Please add me as a contributor to the ignite jira.
> My jira id is malcolmt
> thanks,
> Malcolm
>
--
Alexey Kuznetsov
Please add me as a contributor to the ignite jira.
My jira id is malcolmt
thanks,
Malcolm
Anton V,
Would you mind closing the vote if it passes? Unfortunately, I won't do
this, going offline for significant time.
Denis
On Friday, July 21, 2017, Semyon Boikov wrote:
> +1 binding
>
> On Fri, Jul 21, 2017 at 1:09 PM, Yakov Zhdanov > wrote:
>
> > +1 binding
> >
> > Checked maven build
Github user ascherbakoff closed the pull request at:
https://github.com/apache/ignite/pull/699
---
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
Maxim,
The issue is that it's currently assumed to support job mapping, but it
actually doesn't. However, I agree that AffinityKeyMapped annotation
doesn't fit the use case well. Let's fix documentation and JavaDoc then.
As for the proposed API, it's overcomplicated, took me 15 minutes to
underst
I have never heard about this provider, and it is great they are donating
their resources to the FOSS. I quick glance on their site has reveiled a
couple of issues:
- the page for the "Standard Agreement" returns 404 [1]. I won't be willing to
agree to something I cannot read upfront.
- the proce
Any thoughts?
-Val
On Wed, Jul 19, 2017 at 4:21 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Folks,
>
> Do we currently have any way to set a timeout for an atomic operation? I
> don't see neither a way to do this nor any related documentation.
>
> In the code there are Cach
Guys,
QueryEntity is already too complex. We will deprecate it soon in favor of
brand new SQL API. No need to design FieldConstraint or something similar
at the moment, let's just stick to "Set notNullFields".
On Fri, Jul 21, 2017 at 7:08 PM, Sergey Chugunov
wrote:
> Sergey,
>
> It may be a goo
Alex,
That's a great idea. I would also add an option to dump information on
demand, for case when operation hanged and can't complete.
-Val
On Fri, Jul 21, 2017 at 6:15 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> Igniters,
>
> I've recently stumbled across a situation when occa
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/2337
IGNITE-GG-12512 Introduced explicit ordering of caches start & stop.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite igni
Sergey,
It may be a good idea to distinguish between field constraints (like "not
null" one) which can be applied to only one field; and more complex
constraints that involves more than one field.
In case of field constraints it is better to simplify our model and allow
only one field to appear i
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/2336
IGNITE-5770 Refactor PlatformProcessor to PlatformTarget mechanism
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-57
Sergey, looks good to me!
I thought of something a bit different, where there is a base class
and each constraint type inherits it, but your design is actually better.
Pavel
On Fri, Jul 21, 2017 at 6:38 PM, Sergey Kalashnikov
wrote:
> Hi Pavel,
>
> Good point! What if we make it the following
Hi Pavel,
Good point! What if we make it the following way?
class QueryEntity {
...
/** All constraints to be enforced on this QueryEntity. */
Set constraint;
}
/** Describes constraints that affect one or more fields. */
class QueryConstraint {
/** Names of fields to be checked
+1 binding
On Fri, Jul 21, 2017 at 1:09 PM, Yakov Zhdanov wrote:
> +1 binding
>
> Checked maven build, imported and built examples project in IDEA and run
> several compute exampled and started 2 nodes with default config.
>
> --Yakov
>
> 2017-07-21 12:21 GMT+03:00 Anton Vinogradov :
>
> > +1 (b
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/2335
IGNITE-5806: removed assertion failing Ignite Cache 5 suite
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5806
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite/pull/2334
IGNITE-5712: implementation of context switching for transactions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nizhikov/ignite IGNITE-5712
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2297
---
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 ena
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2313
---
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 ena
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2331
---
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 ena
Dmitriy Pavlov created IGNITE-5806:
--
Summary: IgniteCache5 suite timed out, assertions in sessions
close logic
Key: IGNITE-5806
URL: https://issues.apache.org/jira/browse/IGNITE-5806
Project: Ignite
GitHub user x-kreator opened a pull request:
https://github.com/apache/ignite/pull/2333
ignite-4181
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/x-kreator/ignite ignite-4181
Alternatively you can review and apply these change
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/2332
Ignite 1094
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite ignite-1094
Alternatively you can review and apply these changes as the
Malcolm Taylor created IGNITE-5805:
--
Summary: Fix some alerts identified by lgtm.com
Key: IGNITE-5805
URL: https://issues.apache.org/jira/browse/IGNITE-5805
Project: Ignite
Issue Type: Impro
Github user x-kreator closed the pull request at:
https://github.com/apache/ignite/pull/2325
---
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
Agree,
Since we rely on cache start order during the node start, the same order
should be preserved during activation.
2017-07-21 15:24 GMT+03:00 Jokser :
> Hello Igniters,
>
> Currently order of cache starts/stops operations is not determined during
> cluster activation.
> Some of the cache com
Igniters,
I've recently stumbled across a situation when occasionally Ignite
transactions commit may take up to several seconds while in general most of
the transactions completed in a period of milliseconds.
After a few attempts to analyze this situation with logs, I realized that
this is a no-g
Valentin,
The author of tiket wants to see to provide some API allows to map ComputeJobs
to partitions or keys. If we use @AffinityKeyMapped then you need to enter the
cache name parameter, I think this is not convenient for the user. Therefore, I
propose to extend the existing API.
Having cons
Hello Igniters,
Currently order of cache starts/stops operations is not determined during
cluster activation.
Some of the cache components can be depended on system or utility caches. If
such component starts earlier than system cache on what it's depended, it
can lead to unpredictable errors (e.g
Andrew Mashenkov created IGNITE-5804:
Summary: ScanQuery transformer applies to first results page only.
Key: IGNITE-5804
URL: https://issues.apache.org/jira/browse/IGNITE-5804
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2326
---
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 ena
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/2331
IGNITE-5786 .NET: Fix cache store session handling for cross-cache
transactions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ig
Dmitriy Pavlov created IGNITE-5803:
--
Summary: IgniteCacheTestSuite4: IgniteCacheInvokeReadThroughTest:
6 test failed, stable reproducible locally
Key: IGNITE-5803
URL: https://issues.apache.org/jira/browse/IGNITE
Yury Babak created IGNITE-5802:
--
Summary: Fix all wrong TODO comments in component
Key: IGNITE-5802
URL: https://issues.apache.org/jira/browse/IGNITE-5802
Project: Ignite
Issue Type: Bug
> Green Again
> Again
As if it ever was green :)
Of course +1 on this, let me know if you see any .NET-related failures.
On Fri, Jul 21, 2017 at 1:06 PM, Николай Ижиков
wrote:
> Hello, Igniters.
>
> Also ready to help to #MakeTeamcityGreenAgain !
>
> 21 июля 2017 г. 12:56 PM пользователь "Vyach
Yury Babak created IGNITE-5801:
--
Summary: Externalization for offheap vectors/matrices
Key: IGNITE-5801
URL: https://issues.apache.org/jira/browse/IGNITE-5801
Project: Ignite
Issue Type: Bug
Dmitriy Pavlov created IGNITE-5800:
--
Summary: Umbrella ticket for making Teamcity Green Again
Key: IGNITE-5800
URL: https://issues.apache.org/jira/browse/IGNITE-5800
Project: Ignite
Issue Ty
Yury Babak created IGNITE-5799:
--
Summary: Caching for some intermediate calcs
Key: IGNITE-5799
URL: https://issues.apache.org/jira/browse/IGNITE-5799
Project: Ignite
Issue Type: Improvement
Alexandr Kuramshin created IGNITE-5798:
--
Summary: Logging Ignite configuration at startup
Key: IGNITE-5798
URL: https://issues.apache.org/jira/browse/IGNITE-5798
Project: Ignite
Issue Ty
+1 binding
Checked maven build, imported and built examples project in IDEA and run
several compute exampled and started 2 nodes with default config.
--Yakov
2017-07-21 12:21 GMT+03:00 Anton Vinogradov :
> +1 (binding)
>
> On Fri, Jul 21, 2017 at 12:08 PM, Pavel Tupitsyn
> wrote:
>
> > +1
> >
Hello, Igniters.
Also ready to help to #MakeTeamcityGreenAgain !
21 июля 2017 г. 12:56 PM пользователь "Vyacheslav Daradur" <
daradu...@gmail.com> написал:
> Hi guys.
>
> I vote for #MakeTeamcityGreenAgain. :-)
>
> FYI: it had been described and supported previously[1]
>
> After the completion o
Hi Nikita.
Thanks for the contribution!
If you are curious in BinaryMarshaler and want to continue improve it,
please, take a look to a task [1]
[1] https://issues.apache.org/jira/browse/IGNITE-3244
2017-07-21 12:53 GMT+03:00 Nikita Amelchev :
> Hi, Igniters.
> I fixed issue 5087 - Enum compa
Hi guys.
I vote for #MakeTeamcityGreenAgain. :-)
FYI: it had been described and supported previously[1]
After the completion of my current task I will try to help with this
activity.
[1]
http://apache-ignite-developers.2346864.n4.nabble.com/Test-failures-td14353.html
2017-07-21 12:39 GMT+03:00
Hi, Igniters.
I fixed issue 5087 - Enum comparison fails after marshal-unmarshal with
BinaryMarshaller. The solution is check superclass on enum. I created new
public method isEnum(Class cls) for resolve enum mode in binary class
descriptor. Also I get class name through getDeclaringClass() for enu
Nikolay,
That's also a big problem for me, as reviewer, to accept changes and merge
them to master.
Dmitriy,
Currently we have some contributions *from community* blocked by red
Teamcity.
On Fri, Jul 21, 2017 at 12:47 AM, Nikolay Izhikov
wrote:
> +1 to Dmitry Pavlov from me.
>
> Green team c
+1 (binding)
On Fri, Jul 21, 2017 at 12:08 PM, Pavel Tupitsyn
wrote:
> +1
>
> Checked .NET: nodes start and join from exe file, bat file, NuGet, user
> project.
>
> On Fri, Jul 21, 2017 at 11:49 AM, Vyacheslav Daradur
> wrote:
>
> > +1
> >
> > Build success now. Node starts without issues.
> >
+1
Checked .NET: nodes start and join from exe file, bat file, NuGet, user
project.
On Fri, Jul 21, 2017 at 11:49 AM, Vyacheslav Daradur
wrote:
> +1
>
> Build success now. Node starts without issues.
>
> 2017-07-21 11:38 GMT+03:00 Kozlov Maxim :
>
> > +1
> >
> > > 21 июля 2017 г., в 7:48, Valen
+1
Build success now. Node starts without issues.
2017-07-21 11:38 GMT+03:00 Kozlov Maxim :
> +1
>
> > 21 июля 2017 г., в 7:48, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> написал(а):
> >
> > +1 (binding)
> >
> > On Thu, Jul 20, 2017 at 9:35 PM, Sasha Belyak
> wrote:
> >
> >> +1
> >>
+1
> 21 июля 2017 г., в 7:48, Valentin Kulichenko
> написал(а):
>
> +1 (binding)
>
> On Thu, Jul 20, 2017 at 9:35 PM, Sasha Belyak wrote:
>
>> +1
>>
>> 2017-07-21 5:34 GMT+07:00 Denis Magda :
>>
>>> Igniters,
>>>
>>> Setting off the vote one more time. Hope I’ll be successful this time,
>
Alexey Goncharuk created IGNITE-5797:
Summary: Add latency tracing capability for cache operations
Key: IGNITE-5797
URL: https://issues.apache.org/jira/browse/IGNITE-5797
Project: Ignite
Hi Sergey,
This one looks not very good to me:
> class QueryEntity {
> ...
> Set notNullFields;
> }
What if there are more constraints in future? UNIQUE, CHECK, etc etc?
Instead we could do something like
Set constraints;
Which is easily extendable in future.
Thoughts?
Pavel
On
51 matches
Mail list logo
