[jira] [Created] (IGNITE-6647) Web Console: Implement schema migration

Alexey Kuznetsov created IGNITE-6647: Summary: Web Console: Implement schema migration Key: IGNITE-6647 URL: https://issues.apache.org/jira/browse/IGNITE-6647 Project: Ignite Issue Type:

Re: integrate with prestodb

Shawn, What's the purpose of Presto then if you consider holding all the data in RAM? From what I see, Presto is intended for joining the data stored in different storages. As for the Ignite persistence, here are some performance hints you might need to apply:

Re: Indexing fields of non-POJO cache values

Of course it does, Dmitriy! However as I suggested below, the feature should be optional. The current behavior (not requiring user classes on the server, etc.) would remain the default one. Also, please realize that not everyone stores their data as POJOs or uses Ignite as a JDBC source -- the

Re: integrate with prestodb

Shawn, Then my suggestion would be to enable Ignite persistence [1] that will store the whole data set you have. RAM will keep only a subset for the performance benefits. Ignite SQL is full supported for the persistence, you can even join data RAM and disk only data sets. Plus, your

Re: Persistence per memory policy configuration

Igniters, we should not have Swap in the property names. Swap is something that behaves completely differently from Ignite persistence, and I don't think it should be present within Ignite altogether. D. On Mon, Oct 16, 2017 at 11:17 AM, Vladimir Ozerov wrote: > +1 to

Re: Indexing fields of non-POJO cache values

On Mon, Oct 16, 2017 at 12:35 PM, Andrey Kornev wrote: > [Crossposting to the dev list] > > Alexey, > > Yes, something like that, where the "reference"/"alias" is expressed as a > piece of Java code (as part of QueryEntity definition, perhaps) that is > invoked by

Re: integrate with prestodb

Hello Shawn, Do I understand properly that you have scarce RAM resources and think to exploit Presto as an alternative SQL engine in Ignite that queries both RAM and disk data sets? If that’s the case than just enable Ignite native persistence [1] and you’ll get all the data stored on disk and

Clarification on DROP TABLE command needed

Alex P., Vladimir, I’m finalizing DROP TABLE command documentation and unsure what happens with the following once the command is issued: 1. Do we destroy the underlying cache and purge all its content? 2. What happens to DML operations targeting a table that is somewhere in the middle of the

Re: Persistence per memory policy configuration

+1 to Ivan's suggestion. пн, 16 окт. 2017 г. в 21:00, Ivan Rakov : > *swapPath* is ok for me. It is also consistent with *walPath* and > *walArchivePath*. > > Regarding persistencePath/storagePath, I don't like the idea when path > for WAL is implicitly changed, especially

Re: Persistence per memory policy configuration

*swapPath* is ok for me. It is also consistent with *walPath* and *walArchivePath*. Regarding persistencePath/storagePath, I don't like the idea when path for WAL is implicitly changed, especially when we have separate option for it. WAL and storage files are already located under same

[jira] [Created] (IGNITE-6645) Security issues in Ignite that allows users with write access to datagrid to execute arbitrary code

Denis Magda created IGNITE-6645: --- Summary: Security issues in Ignite that allows users with write access to datagrid to execute arbitrary code Key: IGNITE-6645 URL: https://issues.apache.org/jira/browse/IGNITE-6645

Re: Avoid closing caches on client during cluster restart - determining it's the same cache

Hello Ilya, > > Or do you mean that we ignore cfg in getOrCreateCaches() if name is matched > to already existing cache? Yes, this is what I grasped from the source code. — Denis > On Oct 16, 2017, at 2:29 AM, Ilya Kasnacheev > wrote: > > Hello Denis! > >> we do

[GitHub] ignite pull request #2865: ignite-5741: enable test after fix

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2865 ignite-5741: enable test after fix ignite-5741 was already implemented You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2864: IGNITE-6627 .NET: cache deserialization fails wit...

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/2864 IGNITE-6627 .NET: cache deserialization fails with complex value type… You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2863: Ignite 2.1.6.b1

GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/2863 Ignite 2.1.6.b1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1.6.b1 Alternatively you can review and

[GitHub] ignite pull request #2862: IGNITE-5195 : DataStreamer remap optimization.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2862 IGNITE-5195 : DataStreamer remap optimization. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5195

Re: Ignite ML Models improvements

Vladisav, Thanks for this idea. I`m not sure that this is priority task but anyway I created separate ticket for it(IGNITE-6642). Regards, Yury. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Optimized DML execution: how to name it?

On Mon, Oct 16, 2017 at 12:15 AM, Vladimir Ozerov wrote: > Dmitriy, > > No :-) System properties is bad practice, because in some cases you cannot > change them. Instead, this flag is available in private class > SqlFIeldsQueryEx. So in case user desperately need it, we may

Re: Integration of Spark and Ignite. Prototype.

Hello, guys. I have created example application to run Ignite Data Frame on standalone Spark cluster. With Data Frame API implementation there are no requirements to have any Ignite files on spark worker nodes. I ran this application on the free dataset: ATP tennis match statistics. data -

[jira] [Created] (IGNITE-6642) Integration with PMML

Yury Babak created IGNITE-6642: -- Summary: Integration with PMML Key: IGNITE-6642 URL: https://issues.apache.org/jira/browse/IGNITE-6642 Project: Ignite Issue Type: New Feature Security

[jira] [Created] (IGNITE-6641) PageId handling improvement: PARTITION_ID masking

Sergey Chugunov created IGNITE-6641: --- Summary: PageId handling improvement: PARTITION_ID masking Key: IGNITE-6641 URL: https://issues.apache.org/jira/browse/IGNITE-6641 Project: Ignite

Re: Persistence per memory policy configuration

Igniters, another thing to consider: DataRegionConfiguration.SwapFilePath should be SwapPath, since this is actually not a single file, but a directory path. On Fri, Oct 13, 2017 at 7:53 PM, Denis Magda wrote: > Seems I've got what you’re talking about. > > I’ve tried to

[jira] [Created] (IGNITE-6640) Introduction of models import/export

Yury Babak created IGNITE-6640: -- Summary: Introduction of models import/export Key: IGNITE-6640 URL: https://issues.apache.org/jira/browse/IGNITE-6640 Project: Ignite Issue Type: New Feature

[GitHub] ignite pull request #2860: IGNITE-6637 Statements cache clear on cache destr...

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

Re: Ignite ML Models improvements

Hi Artem, I agree, it is not supported in many frameworks; on the other hand, Spark MLlib supports it [1]. I think it is good thing to check with users if there is a need for this, since we are already on the topic of model importing/exporting. Best regards, Vladisav [1]

[GitHub] ignite pull request #2861: Ignite 5608

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2861 Ignite 5608 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5608 Alternatively you can review and apply

[GitHub] ignite pull request #2833: IGNITE-6362 NPE in Log4J2Logger

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

Re: Ignite ML Models improvements

Hi, Vladislav, I'm not familiar with PMML, but quick googling has shown that Tensorflow, Keras, DL4j and some other major contemporary ML frameworks do not have support of it (at least native). So the question is why should we include it, can you please elaborate? Best regards, Artem. -- Sent

Re: Ignite ML Models improvements

Hi Yury, since we're already on topic for importing/exporting models, just as a thought: maybe we should add support for PMML [1] [2]? Best regards, Vladisav [1] http://dmg.org/pmml/v4-1/GeneralStructure.html [2] https://github.com/jpmml/jpmml-model On Mon, Oct 16, 2017 at 2:20 PM, Yury Babak

[jira] [Created] (IGNITE-6639) Ignite node can try to join to itself

Mikhail Cherkasov created IGNITE-6639: - Summary: Ignite node can try to join to itself Key: IGNITE-6639 URL: https://issues.apache.org/jira/browse/IGNITE-6639 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6638) Add an ability for auto activate BLT

Sergey Puchnin created IGNITE-6638: -- Summary: Add an ability for auto activate BLT Key: IGNITE-6638 URL: https://issues.apache.org/jira/browse/IGNITE-6638 Project: Ignite Issue Type:

[GitHub] ignite pull request #2860: IGNITE-6637 Statements cache clear on cache destr...

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2860 IGNITE-6637 Statements cache clear on cache destroy. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6637

Node-wide and cluster-wide health reflection and reporting

Hello Igniters, A fair share of problems with Ignite deployment stems from the fact that Ignite node doesn't know if it is working properly or it is experiencing problems. Cluster doesn't know either if it has malfunctioning nodes, and if there are, which ones. For example, a recent case, if

[GitHub] ignite pull request #2810: IGNITE-6562: Dynamic service deployment should us...

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

[jira] [Created] (IGNITE-6637) No proper cleanup of statements cache is done on table drop

Alexander Paschenko created IGNITE-6637: --- Summary: No proper cleanup of statements cache is done on table drop Key: IGNITE-6637 URL: https://issues.apache.org/jira/browse/IGNITE-6637 Project:

[jira] [Created] (IGNITE-6636) BinaryStream position integer overflow

Alexandr Kuramshin created IGNITE-6636: -- Summary: BinaryStream position integer overflow Key: IGNITE-6636 URL: https://issues.apache.org/jira/browse/IGNITE-6636 Project: Ignite Issue

[GitHub] ignite pull request #2859: IGNITE-6635

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/2859 IGNITE-6635 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6635 Alternatively you can review and apply these

[jira] [Created] (IGNITE-6635) Minimize H2 usages in InlineIndexHelper

Vladimir Ozerov created IGNITE-6635: --- Summary: Minimize H2 usages in InlineIndexHelper Key: IGNITE-6635 URL: https://issues.apache.org/jira/browse/IGNITE-6635 Project: Ignite Issue Type:

[GitHub] ignite pull request #2857: IGNITE-6634

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

[GitHub] ignite pull request #2858: IGNITE-6521 Update JVM options (default and recom...

GitHub user akuramshingg opened a pull request: https://github.com/apache/ignite/pull/2858 IGNITE-6521 Update JVM options (default and recommendations) for better performance You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2856: IGNITE-6632

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

Re: Avoid closing caches on client during cluster restart - determining it's the same cache

Hello Denis! > we do not check CacheConfiguration settings provided by the client Are you sure about that? I've just tried a scenario where my client got bounced for not having matching EvictionPolicy compared to already deployed servers. Or do you mean that we ignore cfg in getOrCreateCaches()

[GitHub] ignite pull request #2857: IGNITE-6634

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/2857 IGNITE-6634 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6634 Alternatively you can review and apply these

[jira] [Created] (IGNITE-6634) SQL: move IgniteDistributedJoinTestSuite to query suite(s)

Vladimir Ozerov created IGNITE-6634: --- Summary: SQL: move IgniteDistributedJoinTestSuite to query suite(s) Key: IGNITE-6634 URL: https://issues.apache.org/jira/browse/IGNITE-6634 Project: Ignite

Re: integrate with prestodb

Cross-sending to the DEV community. On Mon, Oct 16, 2017 at 12:14 PM, shawn.du wrote: > Hi community, > > I am trying to implement a connector for presto to connect ignite. > I think it will be a very interest thing to connect ignite and presto. > > In fact, currently

[jira] [Created] (IGNITE-6633) Repair basic SQL functionality

Alexei Scherbakov created IGNITE-6633: - Summary: Repair basic SQL functionality Key: IGNITE-6633 URL: https://issues.apache.org/jira/browse/IGNITE-6633 Project: Ignite Issue Type:

[GitHub] ignite pull request #2856: IGNITE-6632

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/2856 IGNITE-6632 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6632 Alternatively you can review and apply these

[jira] [Created] (IGNITE-6632) SQL: simplify GridH2Row infrastructure

Vladimir Ozerov created IGNITE-6632: --- Summary: SQL: simplify GridH2Row infrastructure Key: IGNITE-6632 URL: https://issues.apache.org/jira/browse/IGNITE-6632 Project: Ignite Issue Type:

[GitHub] ignite pull request #2855: IGNITE-6631

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

Re: Optimized DML execution: how to name it?

Dmitriy, No :-) System properties is bad practice, because in some cases you cannot change them. Instead, this flag is available in private class SqlFIeldsQueryEx. So in case user desperately need it, we may advise him to use this class. But I hope it will not be needed. On Sun, Oct 15, 2017 at