date:20191218

Re: Let's remove ignite-schedule module and IgniteScheduler interface

2019-12-18 Thread Anton Vinogradov

My Vote was for 3.0

On Thu, Dec 19, 2019 at 10:44 AM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Is this suggested for 3.0 or 2.8?
>
> I tend to agree with Alexey - API compatibility should be preserved within
> a major version. I would oppose doing such a change in 2.x.
>
> If this is planned for 3.0, then it's a definite +1 from me.
>
> -Val
>
> On Wed, Dec 18, 2019 at 11:34 PM Alexey Kuznetsov 
> wrote:
>
> > Hi!
> >
> > What if some users already using this module?
> > What they should do? Rewrite code?
> > I do not think it is a good idea.
> >
> > My "-1" here.
> >
> > On Thu, Dec 19, 2019 at 8:53 AM Anton Vinogradov  wrote:
> >
> > > ignite-schedule does not look to be properly located or useful.
> > > My +1 here.
> > >
> > > On Thu, Dec 19, 2019 at 8:35 AM Ivan Pavlukhin 
> > > wrote:
> > >
> > > > Ilya,
> > > >
> > > > I think it is a good initiative! Do we really need to keep
> > > > run/callLocall methods at all?
> > > >
> > > > ср, 18 дек. 2019 г. в 17:59, Ilya Kasnacheev :
> > > > >
> > > > > Hello!
> > > > >
> > > > > Since 2.8 is branched, I want to initiate the discussion about
> > removal
> > > of
> > > > > ignite-schedule module.
> > > > >
> > > > > My plan as follows:
> > > > >
> > > > > Remove ignite-schedule module entirely.
> > > > > Move runLocal and callLocal methods from IgniteScheduler to
> > > > IgniteCompute.
> > > > > Delete IgniteScheduler interface with its remaining scheduleLocal()
> > > > methods.
> > > > >
> > > > > Rationale: Ignite is not a tool for local scheduling,
> IgniteScheduler
> > > > does
> > > > > not provide any means of remote scheduling, and I don't think
> anybody
> > > is
> > > > > using that (especially since ignite-schedule is unpublished LGPL
> > > module).
> > > > >
> > > > > I would like to hear opinions as well as positive and negative
> votes
> > > > > towards this. If I won't see any activity, I will go forward with
> > JIRA
> > > > > issue.
> > > > >
> > > > > Previous discussion:
> > https://issues.apache.org/jira/browse/IGNITE-5565
> > > > > We tried to move it to Quartz but it changed semantics in some
> ways.
> > > > >
> > > > > Regards,
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Ivan Pavlukhin
> > > >
> > >
> >
> >
> > --
> > Alexey Kuznetsov
> >
>

Re: Let's remove ignite-schedule module and IgniteScheduler interface

2019-12-18 Thread Valentin Kulichenko

Is this suggested for 3.0 or 2.8?

I tend to agree with Alexey - API compatibility should be preserved within
a major version. I would oppose doing such a change in 2.x.

If this is planned for 3.0, then it's a definite +1 from me.

-Val

On Wed, Dec 18, 2019 at 11:34 PM Alexey Kuznetsov 
wrote:

> Hi!
>
> What if some users already using this module?
> What they should do? Rewrite code?
> I do not think it is a good idea.
>
> My "-1" here.
>
> On Thu, Dec 19, 2019 at 8:53 AM Anton Vinogradov  wrote:
>
> > ignite-schedule does not look to be properly located or useful.
> > My +1 here.
> >
> > On Thu, Dec 19, 2019 at 8:35 AM Ivan Pavlukhin 
> > wrote:
> >
> > > Ilya,
> > >
> > > I think it is a good initiative! Do we really need to keep
> > > run/callLocall methods at all?
> > >
> > > ср, 18 дек. 2019 г. в 17:59, Ilya Kasnacheev :
> > > >
> > > > Hello!
> > > >
> > > > Since 2.8 is branched, I want to initiate the discussion about
> removal
> > of
> > > > ignite-schedule module.
> > > >
> > > > My plan as follows:
> > > >
> > > > Remove ignite-schedule module entirely.
> > > > Move runLocal and callLocal methods from IgniteScheduler to
> > > IgniteCompute.
> > > > Delete IgniteScheduler interface with its remaining scheduleLocal()
> > > methods.
> > > >
> > > > Rationale: Ignite is not a tool for local scheduling, IgniteScheduler
> > > does
> > > > not provide any means of remote scheduling, and I don't think anybody
> > is
> > > > using that (especially since ignite-schedule is unpublished LGPL
> > module).
> > > >
> > > > I would like to hear opinions as well as positive and negative votes
> > > > towards this. If I won't see any activity, I will go forward with
> JIRA
> > > > issue.
> > > >
> > > > Previous discussion:
> https://issues.apache.org/jira/browse/IGNITE-5565
> > > > We tried to move it to Quartz but it changed semantics in some ways.
> > > >
> > > > Regards,
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> > >
> >
>
>
> --
> Alexey Kuznetsov
>

Re: Let's remove ignite-schedule module and IgniteScheduler interface

2019-12-18 Thread Alexey Kuznetsov

Hi!

What if some users already using this module?
What they should do? Rewrite code?
I do not think it is a good idea.

My "-1" here.

On Thu, Dec 19, 2019 at 8:53 AM Anton Vinogradov  wrote:

> ignite-schedule does not look to be properly located or useful.
> My +1 here.
>
> On Thu, Dec 19, 2019 at 8:35 AM Ivan Pavlukhin 
> wrote:
>
> > Ilya,
> >
> > I think it is a good initiative! Do we really need to keep
> > run/callLocall methods at all?
> >
> > ср, 18 дек. 2019 г. в 17:59, Ilya Kasnacheev :
> > >
> > > Hello!
> > >
> > > Since 2.8 is branched, I want to initiate the discussion about removal
> of
> > > ignite-schedule module.
> > >
> > > My plan as follows:
> > >
> > > Remove ignite-schedule module entirely.
> > > Move runLocal and callLocal methods from IgniteScheduler to
> > IgniteCompute.
> > > Delete IgniteScheduler interface with its remaining scheduleLocal()
> > methods.
> > >
> > > Rationale: Ignite is not a tool for local scheduling, IgniteScheduler
> > does
> > > not provide any means of remote scheduling, and I don't think anybody
> is
> > > using that (especially since ignite-schedule is unpublished LGPL
> module).
> > >
> > > I would like to hear opinions as well as positive and negative votes
> > > towards this. If I won't see any activity, I will go forward with JIRA
> > > issue.
> > >
> > > Previous discussion: https://issues.apache.org/jira/browse/IGNITE-5565
> > > We tried to move it to Quartz but it changed semantics in some ways.
> > >
> > > Regards,
> >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
> >
>


-- 
Alexey Kuznetsov

[MTCGA]: new failures in builds [4852901] needs to be handled

2019-12-18 Thread dpavlov . tasks

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 If your changes can lead to this failure(s): We're grateful that you were a 
volunteer to make the contribution to this project, but things change and you 
may no longer be able to finalize your contribution.
 Could you respond to this email and indicate if you wish to continue and fix 
test failures or step down and some committer may revert you commit. 

 *Recently contributed test failed in master 1.0") 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1574644177949948614=%3Cdefault%3E=testDetails

 *Recently contributed test failed in master 2.0") 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8127277359125464421=%3Cdefault%3E=testDetails

 *Recently contributed test failed in master 2.0") 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5593478567511771574=%3Cdefault%3E=testDetails

 *Recently contributed test failed in master 2.0") 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1889833806351045764=%3Cdefault%3E=testDetails

 *Recently contributed test failed in master 0.0") 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5015301887042780026=%3Cdefault%3E=testDetails

 *Recently contributed test failed in master 1.0") 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2270429667022681723=%3Cdefault%3E=testDetails

 *Recently contributed test failed in master 
ClientReconnectCompatibilityTest.TestReconnectToOldNodeDisablesPartitionAwareness
 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=614540287987344876=%3Cdefault%3E=testDetails
 Changes may lead to failure were done by 
 - pavel tupitsyn  
https://ci.ignite.apache.org/viewModification.html?modId=894635
 - nikita amelchev  
https://ci.ignite.apache.org/viewModification.html?modId=894628

 - Here's a reminder of what contributors were agreed to do 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 09:46:07 19-12-2019

Re: Let's remove ignite-schedule module and IgniteScheduler interface

2019-12-18 Thread Anton Vinogradov

ignite-schedule does not look to be properly located or useful.
My +1 here.

On Thu, Dec 19, 2019 at 8:35 AM Ivan Pavlukhin  wrote:

> Ilya,
>
> I think it is a good initiative! Do we really need to keep
> run/callLocall methods at all?
>
> ср, 18 дек. 2019 г. в 17:59, Ilya Kasnacheev :
> >
> > Hello!
> >
> > Since 2.8 is branched, I want to initiate the discussion about removal of
> > ignite-schedule module.
> >
> > My plan as follows:
> >
> > Remove ignite-schedule module entirely.
> > Move runLocal and callLocal methods from IgniteScheduler to
> IgniteCompute.
> > Delete IgniteScheduler interface with its remaining scheduleLocal()
> methods.
> >
> > Rationale: Ignite is not a tool for local scheduling, IgniteScheduler
> does
> > not provide any means of remote scheduling, and I don't think anybody is
> > using that (especially since ignite-schedule is unpublished LGPL module).
> >
> > I would like to hear opinions as well as positive and negative votes
> > towards this. If I won't see any activity, I will go forward with JIRA
> > issue.
> >
> > Previous discussion: https://issues.apache.org/jira/browse/IGNITE-5565
> > We tried to move it to Quartz but it changed semantics in some ways.
> >
> > Regards,
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>

Re: Let's remove ignite-schedule module and IgniteScheduler interface

2019-12-18 Thread Ivan Pavlukhin

Ilya,

I think it is a good initiative! Do we really need to keep
run/callLocall methods at all?

ср, 18 дек. 2019 г. в 17:59, Ilya Kasnacheev :
>
> Hello!
>
> Since 2.8 is branched, I want to initiate the discussion about removal of
> ignite-schedule module.
>
> My plan as follows:
>
> Remove ignite-schedule module entirely.
> Move runLocal and callLocal methods from IgniteScheduler to IgniteCompute.
> Delete IgniteScheduler interface with its remaining scheduleLocal() methods.
>
> Rationale: Ignite is not a tool for local scheduling, IgniteScheduler does
> not provide any means of remote scheduling, and I don't think anybody is
> using that (especially since ignite-schedule is unpublished LGPL module).
>
> I would like to hear opinions as well as positive and negative votes
> towards this. If I won't see any activity, I will go forward with JIRA
> issue.
>
> Previous discussion: https://issues.apache.org/jira/browse/IGNITE-5565
> We tried to move it to Quartz but it changed semantics in some ways.
>
> Regards,



-- 
Best regards,
Ivan Pavlukhin

[jira] [Created] (IGNITE-12468) ClassCastException on thinClient in Apache Ignite

2019-12-18 Thread LEE PYUNG BEOM (Jira)

LEE PYUNG BEOM created IGNITE-12468:
---

 Summary: ClassCastException on thinClient in Apache Ignite
 Key: IGNITE-12468
 URL: https://issues.apache.org/jira/browse/IGNITE-12468
 Project: Ignite
  Issue Type: Bug
  Components: clients
Affects Versions: 2.6
Reporter: LEE PYUNG BEOM


 
{code:java}
ClientConfiguration cfg = new 
ClientConfiguration().setAddresses("127.0.0.1:10800");

try (IgniteClient igniteClient = Ignition.startClient(cfg)) {

System.out.println(">>> Thin client put-get example started.");

final String CACHE_NAME = "put-get-example";

ClientCache cache = 
igniteClient.getOrCreateCache(CACHE_NAME);

Person p = new Person();

//put
HashMap hm = new HashMap();
hm.put(1, p);
cache.put(1, hm);

//get
HashMap map = (HashMap)cache.get(1);
Person p2 = map.get(1);

System.out.format(">>> Loaded [%s] from the cache.\n",p2);

}
catch (ClientException e) {
System.err.println(e.getMessage());
e.printStackTrace();
}
catch (Exception e) {
System.err.format("Unexpected failure: %s\n", e);
e.printStackTrace();
}
{code}
 

I use the thin client of apache-ignite.

I Create a hashmap and put the Person 
class(org.apache.ignite.examples.model.Person) object into it.

And when I take it out of the hashmap, I get the following exceptions:

 
{code:java}
> java.lang.ClassCastException:
> org.apache.enite.internal.binary.BinaryObjectImpl cannot be cast to
> org.apache.engite.examples.model.Person.
{code}
An exception is given in the code below.

 
{code:java}
Person p2 = map.get(1);
{code}
 

However, there is no exception if I modify the code as follows:

 
{code:java}
BinaryObject bo = (BinaryObject) map.get(1);

Person p2 = bo.deserialize();
{code}
I don't think that's necessary. Is there another solution?

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [Webinar] Data Streaming Using Apache Flink and Apache Ignite

2019-12-18 Thread Saikat Maitra

Hi,


The page with the embedded recording and slides link is
https://www.gridgain.com/resources/webinars/data-streaming-using-apache-flink-and-apache-ignite/view
.



You can go directly to the YouTube video at
https://www.youtube.com/watch?v=wM-YVYVU8Lk.



You can go directly to the slides at
https://www.gridgain.com/resources/technical%20presentations/data-streaming-using-apache-flink-and-apache-ignite/view



Regards,

Saikat

On Mon, Dec 9, 2019 at 9:33 PM Saikat Maitra 
wrote:

> Thank you Alexey, yes I think all the webinar videos are recorded and
> shared in youtube.
>
> https://www.youtube.com/results?search_query=gridgain+webinar
>
> I can share the webinar video once it is available.
>
> On Sun, Dec 8, 2019 at 10:28 PM Alexey Zinoviev 
> wrote:
>
>> Great to get a video after to watch and share later, very ineresting case
>>
>> вс, 8 дек. 2019 г., 20:39 Saikat Maitra :
>>
>>> Hi,
>>>
>>> I will be presenting in a webinar about Data Streaming Using Apache Flink
>>> and Apache Ignite on Wednesday, Dec 18th.
>>>
>>>
>>> https://www.gridgain.com/resources/webinars/data-streaming-using-apache-flink-and-apache-ignite
>>>
>>> Apache Ignite is a powerful in-memory computing platform. The Apache
>>> IgniteSink streaming connector enables users to inject Flink data into
>>> the
>>> Ignite cache. Join Saikat Maitra to learn how to build a simple data
>>> streaming application using Apache Flink and Apache Ignite. This stream
>>> processing topology will allow data streaming in a distributed, scalable,
>>> and fault-tolerant manner, which can process data sets consisting of
>>> virtually unlimited streams of events.
>>>
>>> Please feel free to join the webinar.
>>>
>>> Regards,
>>> Saikat
>>>
>>

[jira] [Created] (IGNITE-12467) Thing Client Support for Transactions

2019-12-18 Thread Robert Emanuele (Jira)

Robert Emanuele created IGNITE-12467:


 Summary: Thing Client Support for Transactions
 Key: IGNITE-12467
 URL: https://issues.apache.org/jira/browse/IGNITE-12467
 Project: Ignite
  Issue Type: Bug
  Components: thin client
Affects Versions: 2.7.6
Reporter: Robert Emanuele


I see that https://issues.apache.org/jira/browse/IGNITE-9410 is marked as 
resolved but I have not seen the changes in the python thin client, pyignite.  
Am I looking in the wrong place  
([https://github.com/apache/ignite/tree/master/modules/platforms/python]), or 
is there more work to do?

If there is more work, are there changes that I can port?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

2019-12-18 Thread Maxim Muzafarov

Anton,


Thank you.
Have no objections, let's do it!

On Wed, 18 Dec 2019 at 23:23, Anton Vinogradov  wrote:
>
> Sure,
> You may count on my assistance in case of any problems.
> We're both in the same boat.
>
> But I see no reason to delay the "pme-free switch" merge to 2.8.
> We always have to merge all release features asap to have as much time as
> possible to fix all bugs.
>
> I will replace the "feature activation version" with the "IgniteFeature
> approach" according to your hint and merge it to master and 2.8 shortly in
> case of no objections here.
>
> On Wed, Dec 18, 2019 at 2:16 PM Maxim Muzafarov  wrote:
>
> > Folks,
> >
> > I have no objections. But I would like to count on your support in
> > cases of any release-blocking issues. Can I?
> >
> >
> > Anton,
> >
> > Let's do the following:
> > 1. Merge the issue to the master branch.
> > 2. Wait for two-three weeks of running tests.
> > 3. Check that there are not flaky failures and fix them all otherwise.
> > 4. Cherry-pick commit to the ignite-2.8 branch.
> >
> > WDYT?
> >
> > On Wed, 18 Dec 2019 at 09:26, Nikolay Izhikov  wrote:
> > >
> > > +1 to include PME free switch to 2.8
> > >
> > > ср, 18 дек. 2019 г., 8:31 Anton Vinogradov :
> > >
> > > > Maxim,
> > > > https://issues.apache.org/jira/browse/IGNITE-9913 (Pme-free switch)
> > ready
> > > > to be merged to master.
> > > > How about to include it to the 2.8 too?
> > > >
> > > > On Tue, Dec 17, 2019 at 3:31 PM Ivan Pavlukhin 
> > > > wrote:
> > > >
> > > > > Maxim,
> > > > >
> > > > > I cherry-picked https://issues.apache.org/jira/browse/IGNITE-12424
> > to
> > > > > 2.8 branch.
> > > > >
> > > > > вт, 17 дек. 2019 г. в 15:23, Ivan Pavlukhin :
> > > > > >
> > > > > > Maxim,
> > > > > >
> > > > > > Regarding blocker tickets:
> > > > > > https://issues.apache.org/jira/browse/IGNITE-2176 -- moved to next
> > > > > version
> > > > > > https://issues.apache.org/jira/browse/IGNITE-8552 -- moved to next
> > > > > version
> > > > > > https://issues.apache.org/jira/browse/IGNITE-9489 -- fixed in
> > scope of
> > > > > > another ticket
> > > > > > https://issues.apache.org/jira/browse/IGNITE-2176 -- Anton K. is
> > going
> > > > > > to fix it in next few days
> > > > > >
> > > > > > вт, 17 дек. 2019 г. в 13:30, Maxim Muzafarov :
> > > > > > >
> > > > > > > Ivan,
> > > > > > >
> > > > > > > You should cherry-pick this commit to the ignite-2.8 branch also.
> > > > > > >
> > > > > > > Can you help with the release blocker issue mentioned above? I
> > can
> > > > not
> > > > > > > found the people who are assigned those issues. We need to
> > clarify
> > > > > > > issues status and ask for help if necessary.
> > > > > > >
> > > > > > > On Tue, 17 Dec 2019 at 11:33, Ivan Pavlukhin <
> > vololo...@gmail.com>
> > > > > wrote:
> > > > > > > >
> > > > > > > > Maxim,
> > > > > > > >
> > > > > > > > I merged a fix for thin JDBC default query timeout to master
> > under
> > > > > > > > [1]. What should be the next steps with regard to 2.8 release
> > > > branch?
> > > > > > > >
> > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12424
> > > > > > > >
> > > > > > > > чт, 12 дек. 2019 г. в 13:08, Maxim Muzafarov <
> > mmu...@apache.org>:
> > > > > > > > >
> > > > > > > > > Igniters,
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Here are the 2.8 release BLOCKER issues with unknown status
> > for
> > > > me.
> > > > > > > > > If anyone knows details can you share it?
> > > > > > > > >
> > > > > > > > > IGNITE-2176 [1] - Not valid exceptions in the case when
> > example
> > > > > can't
> > > > > > > > > works (Java 8)
> > > > > > > > > IGNITE-8552 [2] - Unable to use a date as primary key
> > > > > > > > > IGNITE-12227 [3] - Default auto-adjust baseline enabled flag
> > > > > > > > > calculated incorrectly in some cases
> > > > > > > > > IGNITE-9489 [4] -  CorruptedTreeException on index create.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-2176
> > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-8552
> > > > > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-12227
> > > > > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-9489
> > > > > > > > >
> > > > > > > > > On Thu, 12 Dec 2019 at 07:05, Saikat Maitra <
> > > > > saikat.mai...@gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > Hi Ivan,
> > > > > > > > > >
> > > > > > > > > > Thank you so much for your help, I really appreciate it.
> > > > > > > > > >
> > > > > > > > > > I had a quick question and shared in the Jira issue
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-12424
> > > > > > > > > >
> > > > > > > > > > Please review and share your feedback.
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Saikat
> > > > > > > > > >
> > > > > > > > > > On Wed, Dec 11, 2019 at 3:45 AM Ivan Pavlukhin <
> > > > > vololo...@gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > > Saikat,
> > > > > > > > > > >
> > > >

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

2019-12-18 Thread Anton Vinogradov

Sure,
You may count on my assistance in case of any problems.
We're both in the same boat.

But I see no reason to delay the "pme-free switch" merge to 2.8.
We always have to merge all release features asap to have as much time as
possible to fix all bugs.

I will replace the "feature activation version" with the "IgniteFeature
approach" according to your hint and merge it to master and 2.8 shortly in
case of no objections here.

On Wed, Dec 18, 2019 at 2:16 PM Maxim Muzafarov  wrote:

> Folks,
>
> I have no objections. But I would like to count on your support in
> cases of any release-blocking issues. Can I?
>
>
> Anton,
>
> Let's do the following:
> 1. Merge the issue to the master branch.
> 2. Wait for two-three weeks of running tests.
> 3. Check that there are not flaky failures and fix them all otherwise.
> 4. Cherry-pick commit to the ignite-2.8 branch.
>
> WDYT?
>
> On Wed, 18 Dec 2019 at 09:26, Nikolay Izhikov  wrote:
> >
> > +1 to include PME free switch to 2.8
> >
> > ср, 18 дек. 2019 г., 8:31 Anton Vinogradov :
> >
> > > Maxim,
> > > https://issues.apache.org/jira/browse/IGNITE-9913 (Pme-free switch)
> ready
> > > to be merged to master.
> > > How about to include it to the 2.8 too?
> > >
> > > On Tue, Dec 17, 2019 at 3:31 PM Ivan Pavlukhin 
> > > wrote:
> > >
> > > > Maxim,
> > > >
> > > > I cherry-picked https://issues.apache.org/jira/browse/IGNITE-12424
> to
> > > > 2.8 branch.
> > > >
> > > > вт, 17 дек. 2019 г. в 15:23, Ivan Pavlukhin :
> > > > >
> > > > > Maxim,
> > > > >
> > > > > Regarding blocker tickets:
> > > > > https://issues.apache.org/jira/browse/IGNITE-2176 -- moved to next
> > > > version
> > > > > https://issues.apache.org/jira/browse/IGNITE-8552 -- moved to next
> > > > version
> > > > > https://issues.apache.org/jira/browse/IGNITE-9489 -- fixed in
> scope of
> > > > > another ticket
> > > > > https://issues.apache.org/jira/browse/IGNITE-2176 -- Anton K. is
> going
> > > > > to fix it in next few days
> > > > >
> > > > > вт, 17 дек. 2019 г. в 13:30, Maxim Muzafarov :
> > > > > >
> > > > > > Ivan,
> > > > > >
> > > > > > You should cherry-pick this commit to the ignite-2.8 branch also.
> > > > > >
> > > > > > Can you help with the release blocker issue mentioned above? I
> can
> > > not
> > > > > > found the people who are assigned those issues. We need to
> clarify
> > > > > > issues status and ask for help if necessary.
> > > > > >
> > > > > > On Tue, 17 Dec 2019 at 11:33, Ivan Pavlukhin <
> vololo...@gmail.com>
> > > > wrote:
> > > > > > >
> > > > > > > Maxim,
> > > > > > >
> > > > > > > I merged a fix for thin JDBC default query timeout to master
> under
> > > > > > > [1]. What should be the next steps with regard to 2.8 release
> > > branch?
> > > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12424
> > > > > > >
> > > > > > > чт, 12 дек. 2019 г. в 13:08, Maxim Muzafarov <
> mmu...@apache.org>:
> > > > > > > >
> > > > > > > > Igniters,
> > > > > > > >
> > > > > > > >
> > > > > > > > Here are the 2.8 release BLOCKER issues with unknown status
> for
> > > me.
> > > > > > > > If anyone knows details can you share it?
> > > > > > > >
> > > > > > > > IGNITE-2176 [1] - Not valid exceptions in the case when
> example
> > > > can't
> > > > > > > > works (Java 8)
> > > > > > > > IGNITE-8552 [2] - Unable to use a date as primary key
> > > > > > > > IGNITE-12227 [3] - Default auto-adjust baseline enabled flag
> > > > > > > > calculated incorrectly in some cases
> > > > > > > > IGNITE-9489 [4] -  CorruptedTreeException on index create.
> > > > > > > >
> > > > > > > >
> > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-2176
> > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-8552
> > > > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-12227
> > > > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-9489
> > > > > > > >
> > > > > > > > On Thu, 12 Dec 2019 at 07:05, Saikat Maitra <
> > > > saikat.mai...@gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > Hi Ivan,
> > > > > > > > >
> > > > > > > > > Thank you so much for your help, I really appreciate it.
> > > > > > > > >
> > > > > > > > > I had a quick question and shared in the Jira issue
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-12424
> > > > > > > > >
> > > > > > > > > Please review and share your feedback.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Saikat
> > > > > > > > >
> > > > > > > > > On Wed, Dec 11, 2019 at 3:45 AM Ivan Pavlukhin <
> > > > vololo...@gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > > Saikat,
> > > > > > > > > >
> > > > > > > > > > Please see my comment in ticket [1]. Also you can count
> on my
> > > > > > > > > > assistance for the subject. Currently I have time to help
> > > with
> > > > it.
> > > > > > > > > >
> > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12424
> > > > > > > > > >
> > > > > > > > > > вт, 10 дек. 2019 г. в 06:15, Saikat Maitra <
> > > >

Re: How to use spark-2.4 module in Ignite 2.8?

2019-12-18 Thread Denis Magda

Alexey, Nikolay,

Could you please step in and shed some light on what has changed with
Spark? Probably, that's an issue that needs to be addressed before the
release.

-
Denis


On Wed, Dec 18, 2019 at 9:26 AM Stefan Miklosovic <
stefan.mikloso...@instaclustr.com> wrote:

> Hi,
>
> I want to try spark-2.4 module committed recently but I do not see
> spark-2.4 directory in optional dir after I build whole Ignite
> distribution.
>
> I am building like this:
>
> mvn clean install -Pall-java,all-scala,licenses -DskipTests && mvn
> initialize -Prelease
>
> Why is there just "spark" but not "spark-2.4" even "spark-2.4" is in
> all-scala profile?
>
> Cheers
>

Re: Hello world!

2019-12-18 Thread Shishkov Ilya

Ivan, thank you for your response!

18.12.2019, 10:24, "Ivan Pavlukhin" :
> Hi Ilya,
>
> Welcome to Apache Ignite Community!
>
> As I see you already have a contributor role in JIRA (you can work on
> tickets). You can find some contribution guidelines in
> https://github.com/apache/ignite/blob/master/CONTRIBUTING.md
>
> Do not hesitate to ask in case of any questions.
>
> ср, 18 дек. 2019 г. в 10:09, Shishkov Ilya :
>>  Hi everyone on Apache Ignite dev list!
>>
>>  I would like to contribute to Apache Ignite project.
>>
>>  My ASF JIRA username: shishkovilja
>>
>>  With best regards,
>>  Shishkov Ilya,
>>  IT Engineer at SberTech JSC
>
> --
> Best regards,
> Ivan Pavlukhin

Let's remove ignite-schedule module and IgniteScheduler interface

2019-12-18 Thread Ilya Kasnacheev

Hello!

Since 2.8 is branched, I want to initiate the discussion about removal of
ignite-schedule module.

My plan as follows:

Remove ignite-schedule module entirely.
Move runLocal and callLocal methods from IgniteScheduler to IgniteCompute.
Delete IgniteScheduler interface with its remaining scheduleLocal() methods.

Rationale: Ignite is not a tool for local scheduling, IgniteScheduler does
not provide any means of remote scheduling, and I don't think anybody is
using that (especially since ignite-schedule is unpublished LGPL module).

I would like to hear opinions as well as positive and negative votes
towards this. If I won't see any activity, I will go forward with JIRA
issue.

Previous discussion: https://issues.apache.org/jira/browse/IGNITE-5565
We tried to move it to Quartz but it changed semantics in some ways.

Regards,

Re: Cache 6 suite is broken

2019-12-18 Thread Ivan Pavlukhin

So, if nobody objects, I will merge PR [1] on Friday.

[1] https://github.com/apache/ignite/pull/7142

ср, 18 дек. 2019 г. в 13:13, Dmitriy Pavlov :
>
> Hi Ivan, Igniters,
>
> My proposal is to apply PR and take a look to wider statistics in the
> master branch. WDYT?
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 18 дек. 2019 г. в 09:36, Ivan Pavlukhin :
>
> > Igniters,
> >
> > I run tests several times for my PR [1] and results [2] looks somehow
> > better than in master [3]. But the problematic test seems too flaky.
> > So, I cannot decide between 2 options:
> > 1. Apply PR [1].
> > 2. Ignore the problematic test.
> > (Unfortunately do not have a chance to investigate and fix)
> >
> > Someone's opinion would be helpful here.
> >
> > [1] https://github.com/apache/ignite/pull/7142
> > [2]
> > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=pull%2F7142%2Fhead=overview
> > [3]
> > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=%3Cdefault%3E=overview
> >
> > пн, 16 дек. 2019 г. в 13:38, Ivan Pavlukhin :
> > >
> > > An update. After increasing NetworkTimeout [1] the test passes rarely
> > [2].
> > >
> > > [1] https://github.com/apache/ignite/pull/7142/files
> > > [2]
> > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=pull%2F7142%2Fhead=overview
> > >
> > > пн, 16 дек. 2019 г. в 09:07, Ivan Pavlukhin :
> > > >
> > > > Hi,
> > > >
> > > > I noticied that Cache 6 suite finishes badly (exit code 137) almost
> > > > everytime [1] on master. It started recently. A problematic test
> > > > inside is IgniteCache150ClientsTest. I made some attempts to fix the
> > > > test (including reverting recent commits), but had no luck. And a hard
> > > > part here is that I do not know whether the issue was caused by code
> > > > changes or it is infrastructural one. My best attempt was increasing
> > > > NetworkTimeout in test IgniteConfiguration [2]. After that the suite
> > > > was able to finish, but IgniteCache150ClientsTest failed. Also, the
> > > > problematic test seems so flaky, there are many failures in history.
> > > >
> > > > Do not have any really good solution in my mind. I see following
> > options:
> > > > 1. Use workaround in PR [2].
> > > > 2. Ignore test and dig deeper in scope of a separate ticket.
> > > >
> > > > What do you think?
> > > >
> > > > [1]
> > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=%3Cdefault%3E=overview
> > > > [2] https://github.com/apache/ignite/pull/7142/files
> > > > --
> > > > Best regards,
> > > > Ivan Pavlukhin
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
> >



-- 
Best regards,
Ivan Pavlukhin

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

2019-12-18 Thread Maxim Muzafarov

Folks,

I have no objections. But I would like to count on your support in
cases of any release-blocking issues. Can I?


Anton,

Let's do the following:
1. Merge the issue to the master branch.
2. Wait for two-three weeks of running tests.
3. Check that there are not flaky failures and fix them all otherwise.
4. Cherry-pick commit to the ignite-2.8 branch.

WDYT?

On Wed, 18 Dec 2019 at 09:26, Nikolay Izhikov  wrote:
>
> +1 to include PME free switch to 2.8
>
> ср, 18 дек. 2019 г., 8:31 Anton Vinogradov :
>
> > Maxim,
> > https://issues.apache.org/jira/browse/IGNITE-9913 (Pme-free switch) ready
> > to be merged to master.
> > How about to include it to the 2.8 too?
> >
> > On Tue, Dec 17, 2019 at 3:31 PM Ivan Pavlukhin 
> > wrote:
> >
> > > Maxim,
> > >
> > > I cherry-picked https://issues.apache.org/jira/browse/IGNITE-12424 to
> > > 2.8 branch.
> > >
> > > вт, 17 дек. 2019 г. в 15:23, Ivan Pavlukhin :
> > > >
> > > > Maxim,
> > > >
> > > > Regarding blocker tickets:
> > > > https://issues.apache.org/jira/browse/IGNITE-2176 -- moved to next
> > > version
> > > > https://issues.apache.org/jira/browse/IGNITE-8552 -- moved to next
> > > version
> > > > https://issues.apache.org/jira/browse/IGNITE-9489 -- fixed in scope of
> > > > another ticket
> > > > https://issues.apache.org/jira/browse/IGNITE-2176 -- Anton K. is going
> > > > to fix it in next few days
> > > >
> > > > вт, 17 дек. 2019 г. в 13:30, Maxim Muzafarov :
> > > > >
> > > > > Ivan,
> > > > >
> > > > > You should cherry-pick this commit to the ignite-2.8 branch also.
> > > > >
> > > > > Can you help with the release blocker issue mentioned above? I can
> > not
> > > > > found the people who are assigned those issues. We need to clarify
> > > > > issues status and ask for help if necessary.
> > > > >
> > > > > On Tue, 17 Dec 2019 at 11:33, Ivan Pavlukhin 
> > > wrote:
> > > > > >
> > > > > > Maxim,
> > > > > >
> > > > > > I merged a fix for thin JDBC default query timeout to master under
> > > > > > [1]. What should be the next steps with regard to 2.8 release
> > branch?
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12424
> > > > > >
> > > > > > чт, 12 дек. 2019 г. в 13:08, Maxim Muzafarov :
> > > > > > >
> > > > > > > Igniters,
> > > > > > >
> > > > > > >
> > > > > > > Here are the 2.8 release BLOCKER issues with unknown status for
> > me.
> > > > > > > If anyone knows details can you share it?
> > > > > > >
> > > > > > > IGNITE-2176 [1] - Not valid exceptions in the case when example
> > > can't
> > > > > > > works (Java 8)
> > > > > > > IGNITE-8552 [2] - Unable to use a date as primary key
> > > > > > > IGNITE-12227 [3] - Default auto-adjust baseline enabled flag
> > > > > > > calculated incorrectly in some cases
> > > > > > > IGNITE-9489 [4] -  CorruptedTreeException on index create.
> > > > > > >
> > > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-2176
> > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-8552
> > > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-12227
> > > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-9489
> > > > > > >
> > > > > > > On Thu, 12 Dec 2019 at 07:05, Saikat Maitra <
> > > saikat.mai...@gmail.com> wrote:
> > > > > > > >
> > > > > > > > Hi Ivan,
> > > > > > > >
> > > > > > > > Thank you so much for your help, I really appreciate it.
> > > > > > > >
> > > > > > > > I had a quick question and shared in the Jira issue
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-12424
> > > > > > > >
> > > > > > > > Please review and share your feedback.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Saikat
> > > > > > > >
> > > > > > > > On Wed, Dec 11, 2019 at 3:45 AM Ivan Pavlukhin <
> > > vololo...@gmail.com> wrote:
> > > > > > > >
> > > > > > > > > Saikat,
> > > > > > > > >
> > > > > > > > > Please see my comment in ticket [1]. Also you can count on my
> > > > > > > > > assistance for the subject. Currently I have time to help
> > with
> > > it.
> > > > > > > > >
> > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12424
> > > > > > > > >
> > > > > > > > > вт, 10 дек. 2019 г. в 06:15, Saikat Maitra <
> > > saikat.mai...@gmail.com>:
> > > > > > > > > >
> > > > > > > > > > Hi Ilya, Ivan
> > > > > > > > > >
> > > > > > > > > > Thank you for looping me in, I was looking into this issue
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-12424 and
> > > looked into
> > > > > > > > > > JdbcRequest and JdbcRequestHandler but I do not see the
> > > timeout field.
> > > > > > > > > >
> > > > > > > > > > I was hoping the fix would be something similar to adding
> > > these 2 lines
> > > > > > > > > >
> > > > > > > > >
> > >
> > https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/odbc/OdbcRequestHandler.java#L348-L349
> > > > > > > > > >
> > > > > > > > > > Can you please confirm if the Jdbc client side timeout is
> > > even passed to
> > > > >

Re: Cache 6 suite is broken

2019-12-18 Thread Dmitriy Pavlov

Hi Ivan, Igniters,

My proposal is to apply PR and take a look to wider statistics in the
master branch. WDYT?

Sincerely,
Dmitriy Pavlov

ср, 18 дек. 2019 г. в 09:36, Ivan Pavlukhin :

> Igniters,
>
> I run tests several times for my PR [1] and results [2] looks somehow
> better than in master [3]. But the problematic test seems too flaky.
> So, I cannot decide between 2 options:
> 1. Apply PR [1].
> 2. Ignore the problematic test.
> (Unfortunately do not have a chance to investigate and fix)
>
> Someone's opinion would be helpful here.
>
> [1] https://github.com/apache/ignite/pull/7142
> [2]
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=pull%2F7142%2Fhead=overview
> [3]
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=%3Cdefault%3E=overview
>
> пн, 16 дек. 2019 г. в 13:38, Ivan Pavlukhin :
> >
> > An update. After increasing NetworkTimeout [1] the test passes rarely
> [2].
> >
> > [1] https://github.com/apache/ignite/pull/7142/files
> > [2]
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=pull%2F7142%2Fhead=overview
> >
> > пн, 16 дек. 2019 г. в 09:07, Ivan Pavlukhin :
> > >
> > > Hi,
> > >
> > > I noticied that Cache 6 suite finishes badly (exit code 137) almost
> > > everytime [1] on master. It started recently. A problematic test
> > > inside is IgniteCache150ClientsTest. I made some attempts to fix the
> > > test (including reverting recent commits), but had no luck. And a hard
> > > part here is that I do not know whether the issue was caused by code
> > > changes or it is infrastructural one. My best attempt was increasing
> > > NetworkTimeout in test IgniteConfiguration [2]. After that the suite
> > > was able to finish, but IgniteCache150ClientsTest failed. Also, the
> > > problematic test seems so flaky, there are many failures in history.
> > >
> > > Do not have any really good solution in my mind. I see following
> options:
> > > 1. Use workaround in PR [2].
> > > 2. Ignore test and dig deeper in scope of a separate ticket.
> > >
> > > What do you think?
> > >
> > > [1]
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=%3Cdefault%3E=overview
> > > [2] https://github.com/apache/ignite/pull/7142/files
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>

[jira] [Created] (IGNITE-12466) Monitor query pool starvation

2019-12-18 Thread Kirill Tkalenko (Jira)

Kirill Tkalenko created IGNITE-12466:


 Summary: Monitor query pool starvation
 Key: IGNITE-12466
 URL: https://issues.apache.org/jira/browse/IGNITE-12466
 Project: Ignite
  Issue Type: Improvement
Reporter: Kirill Tkalenko
Assignee: Kirill Tkalenko
 Fix For: 2.8


We are having a periodical starvation check ones of 
IGNITE_STARVATION_CHECK_INTERVAL interval.
But that had by system and public pool only.
I want to see the same monitor by query pool.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Let's remove ignite-schedule module and IgniteScheduler interface

Re: Let's remove ignite-schedule module and IgniteScheduler interface

Re: Let's remove ignite-schedule module and IgniteScheduler interface

[MTCGA]: new failures in builds [4852901] needs to be handled

Re: Let's remove ignite-schedule module and IgniteScheduler interface

Re: Let's remove ignite-schedule module and IgniteScheduler interface

[jira] [Created] (IGNITE-12468) ClassCastException on thinClient in Apache Ignite

Re: [Webinar] Data Streaming Using Apache Flink and Apache Ignite

[jira] [Created] (IGNITE-12467) Thing Client Support for Transactions

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

Re: How to use spark-2.4 module in Ignite 2.8?

Re: Hello world!

Let's remove ignite-schedule module and IgniteScheduler interface

Re: Cache 6 suite is broken

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

Re: Cache 6 suite is broken

[jira] [Created] (IGNITE-12466) Monitor query pool starvation

18 matches

Site Navigation

Mail list logo

Footer information