[GitHub] ignite pull request #3518: IGNITE-7690 Move shared memory suite to Ignite Ba...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3518 ---

[GitHub] ignite pull request #3520: IGNITE-7697 Update maven-javadoc-plugin version

GitHub user vveider opened a pull request: https://github.com/apache/ignite/pull/3520 IGNITE-7697 Update maven-javadoc-plugin version * updated maven-javadoc-plugin version * added maven-javadoc-plugin version override to ignite-apache-license-gen * updated

Re: Ignite diagnostic (SQL system views)

Vova, Could you confirm https://issues.apache.org/jira/browse/IGNITE-7527 ready to be merged? On Wed, Feb 14, 2018 at 12:01 PM, Vladimir Ozerov wrote: > I would start with NODES and NODE_ATTRIBUTES as the most simple thing. > > On Tue, Feb 13, 2018 at 4:10 AM, Denis Magda

[jira] [Created] (IGNITE-7699) BinaryMetadata exchange should not be triggered if metadata was not updated

Sergey Chugunov created IGNITE-7699: --- Summary: BinaryMetadata exchange should not be triggered if metadata was not updated Key: IGNITE-7699 URL: https://issues.apache.org/jira/browse/IGNITE-7699

Re: Author in header of class

I agree with Vyacheslav and Anton Vinogradov. Using @author tag can be misleading, Upsource will provide more up-to-date information. On Wed, Feb 14, 2018 at 3:06 PM, Anton Vinogradov wrote: > +1 to Upsource usage. > > Checked that code ownership provided by Upsource

[jira] [Created] (IGNITE-7703) Add a method gets caches in batch

Vladislav Pyatkov created IGNITE-7703: - Summary: Add a method gets caches in batch Key: IGNITE-7703 URL: https://issues.apache.org/jira/browse/IGNITE-7703 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #3523: IGNITE-7699 ObjectBinaryProcessor improvements

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3523 IGNITE-7699 ObjectBinaryProcessor improvements discovery protocol should not be triggered if requested metadata is the same as already existing; logging improvements You can merge

[GitHub] ignite pull request #3524: Fixed handling of state change message in compati...

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/3524 Fixed handling of state change message in compatibility mode. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Author in header of class

Dmitry, > - easy find reviewer and (Patch available queue), > - find test author / mainteiner (MTCGA)>. Upsource suggests reviewers based on changed classes maintainers when we create pull request review. Moreover, it shows all authors of each class in PR, with showing a percentage of

[jira] [Created] (IGNITE-7704) Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations

Alexey Popov created IGNITE-7704: Summary: Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations Key: IGNITE-7704 URL: https://issues.apache.org/jira/browse/IGNITE-7704

Re: Spark data frames

I am definitely interested. Great idea! On Wed, Feb 14, 2018 at 4:32 AM, Nikolay Izhikov wrote: > Hello, Dmitry. > > If other community member are also iterested in that kind of information I > can try to do the talk. > > В Ср, 14/02/2018 в 10:49 +, Dmitry Pavlov пишет:

[GitHub] ignite pull request #3522: IGNITE-7452: Make Linear SVM example for multi - ...

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/3522 IGNITE-7452: Make Linear SVM example for multi - classification You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Author in header of class

Hi Folks, Listing from git annotate are not informative because there are many contributors change same place of code. Code author information can help us to solve 2 issues for new community members: - easy find reviewer and (Patch available queue), - find test author / mainteiner (MTCGA). So I

Author in header of class

Hello Ignite Community! My name is Anton. I joined to community some time ago and I want to contribute to Apache Ignite. I would be want to make my first proposal. I noticed that Ignite don't have author description in header of classes unlike many other apache projects. I propose to use

[GitHub] ignite pull request #3521: ignite-7594

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/3521 ignite-7594 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilantukh/ignite ignite-7594 Alternatively you can review and apply these changes

Re: Author in header of class

Hi Anton, Apache Ignite is licensed under the Apache License Version 2.0, which does not allow to use author tag in java code [1]. [1] http://directory.apache.org/fortress/coding-standards.html#classinterface-headers On Wed, Feb 14, 2018 at 11:23 AM, Антон Калашников wrote:

Re: Author in header of class

Anton, All listed info can be gained from git history. On Wed, Feb 14, 2018 at 1:01 PM, Дмитрий Рябов wrote: > For the first profit you should see maintainer table [1]. > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/How+ >

[jira] [Created] (IGNITE-7700) SQL system view for list of nodes

Aleksey Plekhanov created IGNITE-7700: - Summary: SQL system view for list of nodes Key: IGNITE-7700 URL: https://issues.apache.org/jira/browse/IGNITE-7700 Project: Ignite Issue Type:

Re: Ignite diagnostic (SQL system views)

I would start with NODES and NODE_ATTRIBUTES as the most simple thing. On Tue, Feb 13, 2018 at 4:10 AM, Denis Magda wrote: > Alex P, sounds like a good plan for me. > > Vladimir, do you have any suggestions or corrections? > > — > Denis > > > On Feb 12, 2018, at 4:57 AM, Alex

Re: Author in header of class

For the first profit you should see maintainer table [1]. [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewProcessandMaintainers 2018-02-14 11:42 GMT+03:00 Vyacheslav Daradur : > Hi Anton, > > Apache Ignite is licensed under the

Spark data frames

Hi Nikolay, I've notices there are a number of very lively discussions on dev list about SparkDataFrames. But I, for example, can't fully understand it because it is not well-known code for me. I suppose Ignite community has other members, which are not aware of recent feature SparkDataFrame and

[jira] [Created] (IGNITE-7701) SQL system view for node attributes

Aleksey Plekhanov created IGNITE-7701: - Summary: SQL system view for node attributes Key: IGNITE-7701 URL: https://issues.apache.org/jira/browse/IGNITE-7701 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7708) Ignite Compute has flaky failures

Dmitriy Pavlov created IGNITE-7708: -- Summary: Ignite Compute has flaky failures Key: IGNITE-7708 URL: https://issues.apache.org/jira/browse/IGNITE-7708 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-7705) DIscoverySpi should inherit networkTimeout from IgniteConfiguration

Alexey Popov created IGNITE-7705: Summary: DIscoverySpi should inherit networkTimeout from IgniteConfiguration Key: IGNITE-7705 URL: https://issues.apache.org/jira/browse/IGNITE-7705 Project: Ignite

[jira] [Created] (IGNITE-7707) Read lock for key/keys

Mikhail Cherkasov created IGNITE-7707: - Summary: Read lock for key/keys Key: IGNITE-7707 URL: https://issues.apache.org/jira/browse/IGNITE-7707 Project: Ignite Issue Type: Improvement

Apache EU Roadshow CFP Closing Soon (23 February)

Hello Everyone This is an initial reminder to let you all know that we are holding an Apache EU Roadshow co-located with FOSS Backstage in Berlin on 13^th and 14^th June 2018. https://s.apache.org/tCHx The Call for Proposals (CFP) for the Apache EU Roadshow is currently open and will close

[jira] [Created] (IGNITE-7706) Data streamer hangs due to uploading instances of updated class

Roman Guseinov created IGNITE-7706: -- Summary: Data streamer hangs due to uploading instances of updated class Key: IGNITE-7706 URL: https://issues.apache.org/jira/browse/IGNITE-7706 Project: Ignite

Re: IGNITE-5714 Context switching for pessimistic transactions

1) The essential problem lies in *IgniteTxAdapter#threadId*. Thread id is set when transaction is created and afterwards is transferred between nodes by GridDistributedTx requests\responses when we perform put\get operations. When we suspend and resume transaction, thread id is got changed

[GitHub] ignite pull request #3527: IGNITE-7681: SQL COPY performance fixes and perfo...

GitHub user gg-shq opened a pull request: https://github.com/apache/ignite/pull/3527 IGNITE-7681: SQL COPY performance fixes and performance test You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7681

[jira] [Created] (IGNITE-7709) SQL COPY: fix file name handling

Kirill Shirokov created IGNITE-7709: --- Summary: SQL COPY: fix file name handling Key: IGNITE-7709 URL: https://issues.apache.org/jira/browse/IGNITE-7709 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #3526: IGNITE-7709: SQL COPY file name handling fix

GitHub user gg-shq opened a pull request: https://github.com/apache/ignite/pull/3526 IGNITE-7709: SQL COPY file name handling fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7709 Alternatively

[GitHub] ignite pull request #3525: Ignite 7517

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3525 Ignite 7517 You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-7517 Alternatively you can review and

Re: Ignite work directory usage?

> because mappings generated by different nodes are supposed to be always the same Most file systems have atomic rename(). This means we should have two-phase write of files into the folder in question. Step one - create ".class.tmp" file, write data into it; Step two - rename file to

[jira] [Created] (IGNITE-7702) Adopt KNN classification to the new Dataset from dataset package

Aleksey Zinoviev created IGNITE-7702: Summary: Adopt KNN classification to the new Dataset from dataset package Key: IGNITE-7702 URL: https://issues.apache.org/jira/browse/IGNITE-7702 Project:

Re: Author in header of class

+1 to Upsource usage. Checked that code ownership provided by Upsource is correct. On Wed, Feb 14, 2018 at 2:22 PM, Vyacheslav Daradur wrote: > Dmitry, > > > - easy find reviewer and (Patch available queue), > > - find test author / mainteiner (MTCGA)>. > Upsource suggests

Re: Spark data frames

Hello, Dmitry. If other community member are also iterested in that kind of information I can try to do the talk. В Ср, 14/02/2018 в 10:49 +, Dmitry Pavlov пишет: > Hi Nikolay, > > I've notices there are a number of very lively discussions on dev list about > SparkDataFrames. But I, for

Re: IgniteSet implementation: changes required

Hello, Igniters! I agree that solution with separate caches is not acceptable for a large number of sets. So, I want to suggest one more way to implement IgniteSet that will introduce element indexes (similar to IgniteQueue). To implement this we can add head/tail indexes to IgniteSet header and

Re: Spark data frames

Dmitry, it's a great idea! Nikolay, I also have the interest to get familiar with Spark Data Frames integration. I'd prefer webinar of the format similar to "Ignite Persistent Store Walkthrough" by Denis Magda, which has been presented some times ago. On Wed, Feb 14, 2018 at 5:03 PM, Dmitriy

Webinar: "Getting Started with Apache Ignite as a Distributed Database (Today at 1 a.m. Pacific)

Igniters, Valentin Kulichenko is hosting a free webinar today at 11 a.m.. Pacific time that will give you the tools and blueprint to build your very own distributed database using Apache Ignite. This webinar will be recorded. You can register to addend the event live or catch the recording from

SQL Compliance documentation

Igniters, Apache Ignite's compliance to SQL:1999 (Core) is now documented on readme.io[1] as well as on Wikipedia[2]. SQL folks, check it out and let me know if there needs to be any correction. Thanks to Aleksandr Volkov for validating Ignite's compliance with SQL99 Core specification. [1]

[jira] [Created] (IGNITE-7711) Explain the case-sensitivity of schema and table/cache

Denis Magda created IGNITE-7711: --- Summary: Explain the case-sensitivity of schema and table/cache Key: IGNITE-7711 URL: https://issues.apache.org/jira/browse/IGNITE-7711 Project: Ignite Issue

[GitHub] ignite pull request #3527: IGNITE-7681: SQL COPY performance fixes and perfo...

Github user gg-shq closed the pull request at: https://github.com/apache/ignite/pull/3527 ---

Fwd: Travel Assistance applications open. Please inform your communities

Folks, If anyone is willing to go and present Ignite in Canada then please enroll. I’ll can share a dozen of Ignite related slides/topics that you can use for your talks. — Denis > Begin forwarded message: > > From: Gavin McDonald > Subject: Travel Assistance

Re: API to enlist running user tasks

On Tue, Feb 13, 2018 at 8:22 PM, Nikolay Izhikov wrote: > Dmitriy > > I thought about those type of tasks that require custom user code to be > executed inside Ignite. > > Your suggestion make sense for me also. Let's include SQL queries. > Should we include ScanQuery,

[GitHub] ignite pull request #3528: IGNITE-7681: SQL COPY: Implementing performance i...

GitHub user gg-shq opened a pull request: https://github.com/apache/ignite/pull/3528 IGNITE-7681: SQL COPY: Implementing performance improvements You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-7710) copy from csv fails to find existing table (intermittently)

Pavel Kuznetsov created IGNITE-7710: --- Summary: copy from csv fails to find existing table (intermittently) Key: IGNITE-7710 URL: https://issues.apache.org/jira/browse/IGNITE-7710 Project: Ignite

.NET: ISslContextFactory should be empty

Igniters, Alexey, Igor, I'd like to discuss recently added ISslContextFactory interface. https://github.com/apache/ignite/commit/e58aae48b67c74307703d2ae44fe8e3cd4b9649a "Factory" implies a "CreateInstace" or a similar method, see CacheConfigurationCacheStoreFactory or ExpiryPolicyFactory as an

[GitHub] ignite pull request #3507: IGNITE-7652: ContinuousQueryWithTransformer examp...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3507 ---

Re: Transport compression (not store compression)

Hello, Igniters. I have not seen such use-cases, where heavy client ignite node placed in a much worse network than the server. I'm not sure we should encourage a bad cluster architecture. Usually, in my use-cases, the servers and clients locate in the same network. And if the cluster has SSL