[jira] [Created] (IGNITE-7352) Java 9: rework "sun.misc.SharedSecrets" and "sun.misc.JavaNioAccess" usages

2018-01-04 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-7352:
---

 Summary: Java 9: rework "sun.misc.SharedSecrets" and 
"sun.misc.JavaNioAccess" usages
 Key: IGNITE-7352
 URL: https://issues.apache.org/jira/browse/IGNITE-7352
 Project: Ignite
  Issue Type: Task
  Components: general
Reporter: Vladimir Ozerov
 Fix For: 2.4


*Problem*
We have two usages of {{sun.misc.SharedSecrets}} and {{sun.misc.JavaNioAccess}} 
in the project. Both methods do the same thing - convert native pointer to 
{{ByteBuffer}}:
{{GridUnsafe.wrapPointer}} 
{{PageMemoryImpl.wrapPointer}}

Java9 cannot compile it because these classes were moved to 
{{jdk.internal.misc}} package.

*Suggested fix*
1) Remove {{PageMemoryImpl.wrapPointer}} method and use 
{{GridUnsafe.wrapPointer}} instead.
2) Rework {{GridUnsafe.wrapPointer}} to reflection-based approach.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (IGNITE-7351) Create a page for continuous queries

2018-01-04 Thread Denis Magda (JIRA)
Denis Magda created IGNITE-7351:
---

 Summary: Create a page for continuous queries
 Key: IGNITE-7351
 URL: https://issues.apache.org/jira/browse/IGNITE-7351
 Project: Ignite
  Issue Type: Sub-task
  Components: site
Reporter: Denis Magda
 Fix For: 2.4


Create a page for continuous queries putting it under Features menu on the 
site. This capability is a strong distinguisher from relational databases that 
do not support continuous notifications and processing built around them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: Hello

2018-01-04 Thread Denis Magda
Hello Mohan,

Please subscribe to both dev and user lists:
https://ignite.apache.org/community/resources.html#mail-lists

Get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Project setup in Intellij IDEA:
https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup

Once you got familiar and were able to run a few examples, you should pick
a Jira ticket you would like to start on. Send an email to the dev list sharing 
your JIRA id, so we can add you as a contributor in Jira.

These are the easy tickets to start with:
https://issues.apache.org/jira/browse/IGNITE-4549?jql=project%20%3D%20IGNITE%20AND%20labels%20in%20(newbie)%20and%20status%20%3D%20OPEN

While those are more advanced but appealing:
https://ignite.apache.org/community/contribute.html#pick-tickets 


Looking forward to your contributions!

Denis

> On Jan 4, 2018, at 9:27 AM, Mohan Chegu  wrote:
> 
> I would like to spend weekly 8 hours of time to contribute on open source
> projects. I am interested with Apache Ignite. Please let me know the
> process involved for the same.
> 
> Thanks
> Mohan
> https://www.linkedin.com/in/mohan-gupta-chegu-4a828a19/



Re: Spark data frames integration merged

2018-01-04 Thread Denis Magda
Revin,

As as side note, do you have a public article published or any other relevant 
material that explains how Ignite is used at Expedia?

You would help the community out a lot if such information is referenced from 
this page:
https://ignite.apache.org/provenusecases.html 


—
Denis

> On Jan 3, 2018, at 11:24 AM, Revin Chalil  wrote:
> 
> Thank you and this is great news. 
> 
> We currently use the Ignite cache as a Reference dataset RDD in Spark, 
> convert it into a spark DataFrame and then join this DF with the 
> incoming-data DF. I hope we can change this 3 step process to a single step 
> with the Spark DF integration. If so, would index / affinitykeys on the join 
> columns help with performance? We currently do not have them defined on the 
> Reference dataset. Are there examples available joining ignite DF with Spark 
> DF? Also, what is the best way to get the latest executables with the 
> IGNITE-3084 included? Thanks again. 
> 
> 
> On 12/29/17, 10:34 PM, "Nikolay Izhikov"  wrote:
> 
>Thank you, guys.
> 
>Val, thanks for all reviews, advices and patience.
> 
>Anton, thanks for ignite wisdom you share with me.
> 
>Looking forward for next issues :)
> 
>P.S Happy New Year for all Ignite community!
> 
>В Пт, 29/12/2017 в 13:22 -0800, Valentin Kulichenko пишет:
>> Igniters,
>> 
>> Great news! We completed and merged first part of integration with
>> Spark data frames [1]. It contains implementation of Spark data
>> source which allows to use DataFrame API to query Ignite data, as
>> well as join it with other data frames originated from different
>> sources.
>> 
>> Next planned steps are the following:
>> - Implement custom execution strategy to avoid transferring data from
>> Ignite to Spark when possible [2]. This should give serious
>> performance improvement in cases when only Ignite tables participate
>> in a query.
>> - Implement ability to save a data frame into Ignite via
>> DataFrameWrite API [3].
>> 
>> [1] https://issues.apache.org/jira/browse/IGNITE-3084
>> [2] https://issues.apache.org/jira/browse/IGNITE-7077
>> [3] https://issues.apache.org/jira/browse/IGNITE-7337
>> 
>> Nikolay Izhikov, thanks for the contribution and for all the hard
>> work!
>> 
>> -Val
> 
> 



[GitHub] ignite pull request #3325: IGNITE-7322: Distributed MLP training

2018-01-04 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/3325


---


Re: IGNITE-6252 patch

2018-01-04 Thread Denis Magda
Hello,

I hope Igor R. will review the changes as soon as prolonged holidays are over.

—
Denis

> On Jan 2, 2018, at 5:24 PM, Sunny Chan, CLSA  wrote:
> 
> Hello,
> 
> I have replied to the comment in November and I am okay with your updated 
> patch – what do I need to do to move this forward?
> 
> From: Nikolai Tikhonov [mailto:ntikho...@apache.org]
> Sent: Tuesday, October 31, 2017 11:50 PM
> To: dev@ignite.apache.org; Sunny Chan, CLSA
> Subject: Re: IGNITE-6252 patch
> 
> Hello,
> 
> Thank you for your contribution! I've reviewed your changes and left comment 
> to ticket. Could you look jira 
> https://issues.apache.org/jira/browse/IGNITE-6252?
> 
> On Mon, Oct 30, 2017 at 10:57 AM, Sunny Chan, CLSA 
> > wrote:
> Hello,
> 
> During our testing we have found an issue and I have raised a JIRA ticket 
> https://issues.apache.org/jira/browse/IGNITE-6252. I have also provided a 
> patch that would fix the issue. Could someone take a look and see whether the 
> patch is acceptable?
> 
> Thanks.
> The content of this communication is intended for the recipient and is 
> subject to CLSA Legal and Regulatory Notices.
> These can be viewed at https://www.clsa.com/disclaimer.html or sent to you 
> upon request.
> CLSA is ISO14001 certified and committed to reducing environmental impact.
> 
> The content of this communication is intended for the recipient and is 
> subject to CLSA Legal and Regulatory Notices.
> These can be viewed at https://www.clsa.com/disclaimer.html or sent to you 
> upon request.
> CLSA is ISO14001 certified and committed to reducing environmental impact.



Hello

2018-01-04 Thread Mohan Chegu
I would like to spend weekly 8 hours of time to contribute on open source
projects. I am interested with Apache Ignite. Please let me know the
process involved for the same.

Thanks
Mohan
https://www.linkedin.com/in/mohan-gupta-chegu-4a828a19/


Re: Hello

2018-01-04 Thread Pavel Tupitsyn
Hi Alexey,

Welcome to Ignite community!

I've added contributor permissions to your Jira account,
you should be able to assign issues to yourself and put them to "In
Progress".

IGNITE-7281 is about .NET, so have a look at .NET development guidelines on
wiki:
https://cwiki.apache.org/confluence/display/IGNITE/Ignite.NET+Development

Thanks,
Pavel

On Thu, Jan 4, 2018 at 11:34 AM, Алексей Рохин 
wrote:

> I would like to join apache ignite development.
> My JIRA ID is  rokhin
>
> Going to start from IGNITE-7281.
>
>
> BR


[jira] [Created] (IGNITE-7350) Distributed MLP cleanup/refactoring

2018-01-04 Thread Yury Babak (JIRA)
Yury Babak created IGNITE-7350:
--

 Summary: Distributed MLP cleanup/refactoring
 Key: IGNITE-7350
 URL: https://issues.apache.org/jira/browse/IGNITE-7350
 Project: Ignite
  Issue Type: Bug
  Components: ml
Reporter: Yury Babak
Assignee: Yury Babak


Current state of MLP not so good, so we need improve it and may be rewrite some 
parts of this NN.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: Connection problem between client and server

2018-01-04 Thread Denis Mekhanikov
Jeff,

Your have indeed a lot of data sent over discovery. Almost all of it is
taken by node attributes. Try reducing Java classpath and PATH environment
variable. Also increasing of TCP window could help, because now a lot of
small messages are sent instead of a few big ones.

Cross-sending it to dev list:
Guys, turns out, we are sending a lot of irrelevant information in
discovery messages. Some messages contain *TcpDiscoveryNode* objects, which
in turn have such attributes like *PATH, java.class.path,
sun.boot.class.path, java.library.path, org.apache.ignite.jvm.args, *etc.
Some of these attributes may contain huge strings, that can sum up to
megabytes of data.

I think, we should filter-out such attributes, because they are not used
anywhere, but  make messages grow enormous and slow down discovery.

What do you think?

Denis

чт, 4 янв. 2018 г. в 10:42, Jeff Jiao :

> dev2.cap <
> http://apache-ignite-users.70518.x6.nabble.com/file/t757/dev2.cap>
>
> Hi Denis,
>
> the attachment is the packages that server transport to client when
> connect,
> we catched it using tool (Microsoft network monitor), can you please take a
> look and see what you can find?
>
> we only configured 12 caches in our Ignite, most of them have 3 or 4
> indexes, only few has 7 or 8 indexes configured...
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


iginite participation

2018-01-04 Thread Алексей Рохин
I would like to join apache ignite development.
My JIRA ID is  r okhin

Going to start from IGNITE-7281.


BR