Re: Maven. Issues with flatten plugin

The problem is solved by updating flatten-maven-plugin version to 1.0.1. Nikolay, please, double check it. If it really solves the problem, please, fill the ticket (or point to existing one), so I can update it and check impact on release procedure. > On 1 Mar 2018, at 17:04, Nikolay Izhikov

[jira] [Created] (IGNITE-7861) Web console: invalid column on Activity details modal

Vasiliy Sisko created IGNITE-7861: - Summary: Web console: invalid column on Activity details modal Key: IGNITE-7861 URL: https://issues.apache.org/jira/browse/IGNITE-7861 Project: Ignite

Re: Transparent Data Encryption (TDE) in Apache Ignite

Dmitriy R., Nilokay, Thanks for the analysis and handout of the architectural design. No doubts, it would be a valuable addition to Ignite. I would encourage you creating an IEP on the wiki and break the work into pieces discussing specific part with the community. -- Denis On Thu, Mar 1,

Re: Transparent Data Encryption (TDE) in Apache Ignite

> Got it, thanks! In this case this sounds very useful. Do we understand the > performance impact? I don't think we fully understand it. It's a question of additional research and benchmarking. So preliminary conclusions, based on common sense and my experiense of usage Ignite in production,

Re: Transparent Data Encryption (TDE) in Apache Ignite

On Fri, Mar 2, 2018 at 8:29 AM, Nikolay Izhikov wrote: > Hello, Dmitriy. > > Thank you for feedback! > > > Will it be supported? > > Yes. > > TDE shouldn't broke any of existing Ignite features. > It adds some encrypt/decrypt level when we writing and reading pages > in/from

Re: Transparent Data Encryption (TDE) in Apache Ignite

Hello, Dmitriy. Thank you for feedback! > Will it be supported? Yes. TDE shouldn't broke any of existing Ignite features. It adds some encrypt/decrypt level when we writing and reading pages in/from PDS. В Пт, 02/03/2018 в 07:29 +0300, Dmitriy Setrakyan пишет: > I have looked at the design,

Re: Transparent Data Encryption (TDE) in Apache Ignite

I have looked at the design, but could not find anything about running SQL queries against the encrypted data. Will it be supported? D. On Thu, Mar 1, 2018 at 8:05 PM, Nikolay Izhikov wrote: > Hell, Dima! > > Thank you for document! > > I'm ready to implement this feature

Enabling swap space and Ignite Persistence

Engineers, How does persistence and swap work when both are enabled? I was under the impression that for a data region you can either have swap or persistence configured at a time, but not both. Please clarify. Thanks, -Prachi

Re: Next Steps: GA Grid: Request to contribute GA library to Apache Ignite

Yury, I have reviewed and removed unnecessary pom files. In addition, I have updated my branch from master. Thanks. Best, Turik -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts

+1. Low level timeouts that we still have in discovery and communication are very hard to explain and I doubt there is anyone who fully understands how they currently work. They bring a lot of complexity and almost zero value. Let's deprecate them and leave only failureDetectionTimeout plus other

Re: Maven. Issues with flatten plugin

>> Anton, Vyacheslav — are you proposing assembly process shift to package >> phase, yet leaving the special profile for assembly itself? I'm talking about compile and package processes like it has been until 2.1 release. On Thu, Mar 1, 2018 at 6:00 PM, Dmitry Pavlov

Re: Apache Ignite 2.4 release

Hi Vladimir, The regression, as well as the performance, is definitely bad. Please work with Sergey to see how much time he needs to rerun the whole test set if you merge the changes. I would target the end of the next week as a release date if the vote goes well. Probably, we can run the test

Re: Ignite Thin clients for Node.js, Python, PHP

Agree with Vladimir and Denis. I don't think JSON has any place in the thin client protocol, which is a binary protocol designed to be efficient, with clearly defined data format. We already have JSON in "REST" client. On Thu, Mar 1, 2018 at 8:15 PM, Denis Magda wrote: >

Re: Ignite Thin clients for Node.js, Python, PHP

Totally share Vladimir's stance. Let's support the scope that already exists in the protocol and think about the future later. The users will definitely guide us to a right direction :) -- Denis On Thu, Mar 1, 2018 at 7:12 AM, Vladimir Ozerov wrote: > I would extract

Re: Thin client: Java bindings

Alexey, outstanding progress! Can't wait the client rolled out to Ignite users. Please create a doc JIRA ticket for 2.5 release and assign to Prachi for review. -- Denis On Thu, Mar 1, 2018 at 4:56 AM, Alexey Kukushkin wrote: > Igniters! > > Could you please help

Re: Transparent Data Encryption (TDE) in Apache Ignite

Hell, Dima! Thank you for document! I'm ready to implement this feature with you. Igniters, please, share you thoughts about proposed design [1] https://1drv.ms/w/s!AqZdfua4UpmuhneoVhOCiXSUBGIf В Чт, 01/03/2018 в 15:46 +0300, Дмитрий Рябов пишет: > Hello, Igniters! > > I investigated the

Re: Apache Ignite 2.4 release

Hi, We found one nasty regression in DROP COLUMN feature and fixed it today. Another problem is performance - we found that recent changes to TCP communication metrics caused considerable slowdown in in-memory mode. I almost fixed it and will merge the fix in the nearest day if benchmarks are ok.

Re: Ignite Thin clients for Node.js, Python, PHP

I would extract compute tasks into separate scope. It is better to keep focus on protocol things and basic language support for now. Once we have basic client API in production-ready state, we could consider adding JavaScript to our core compute feature set and then extend it to the clients (which

Re: Maven. Issues with flatten plugin

Hi, I think we should solve initial problem: "We have to include all transitive dependencies into poms". I've faced with it during Direct IO plugin development. I am sure it is not best practice. Because 1st level dependency version change will require us to update 2nd level dependencies

Re: Thin client / Binary protocol: questions

Denis and All, The links you asked for: - Java thin client development branch - Code review in Upsource - Thin client documentation

[GitHub] ignite pull request #3588: IGNITE-7789: fix IgniteClientReconnectApiExceptio...

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

Re: Maven. Issues with flatten plugin

Anton, Vyacheslav — are you proposing assembly process shift to package phase, yet leaving the special profile for assembly itself? > On 1 Mar 2018, at 14:36, Vyacheslav Daradur wrote: > > I agree with Anton, especially with the following statement: >>> Ignite should be

Re: Ignite Thin clients for Node.js, Python, PHP

With regards of thin clients for dynamically typed languages, I think Ignite needs two following features to shine: - Ability to pass JSON to such clients, turn JSON Objects into a BinaryObjects, which will give ability to index top-level keys in such JSON with SQL Indexing. Of course this should

[jira] [Created] (IGNITE-7860) JDBC thin driver: set default socket buffer sizes to greater value

Vladimir Ozerov created IGNITE-7860: --- Summary: JDBC thin driver: set default socket buffer sizes to greater value Key: IGNITE-7860 URL: https://issues.apache.org/jira/browse/IGNITE-7860 Project:

Re: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts

I agree with you. I think we could restrict usage of e.g. setConnectTimeout/setSocketTimeout to people extending SPIs, since different implementations may need different values. However, for user configurations we should only expose timeouts we can explain, everything else should have reasonable

Re: Maven. Issues with flatten plugin

Petr. Thank you for trying! Did you remove 'test' dependencies before running commands? Because I commit in master only correct pom.xml for current build process, of course. But, to make things works I have to copy paste transitive dependencies from spark-core. 1 марта 2018 г. 4:55 PM

IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts

Hi Igniters, We often see similar questions from users and customers related to IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations. And we see several side-effects after incorrect timeout configuration. I tried to briefly describe these timeout settings

[jira] [Created] (IGNITE-7859) SQL streaming support via native API

Alexander Paschenko created IGNITE-7859: --- Summary: SQL streaming support via native API Key: IGNITE-7859 URL: https://issues.apache.org/jira/browse/IGNITE-7859 Project: Ignite Issue

Re: Maven. Issues with flatten plugin

> > I don't get what is the point. > Did you try to reproduce issue? > Or should I provide full traces to you? > My point in inability to fully understand and describe the problem in terms of mechanism which causes it. For now I can see only indirect guessing. And yes, I’ve run your

[jira] [Created] (IGNITE-7858) "Cannot find cache" error for existing cache on unstable topology

Alexey Kukushkin created IGNITE-7858: Summary: "Cannot find cache" error for existing cache on unstable topology Key: IGNITE-7858 URL: https://issues.apache.org/jira/browse/IGNITE-7858 Project:

Re: Maven. Issues with flatten plugin

> Which pom.xml? From the module modules/spark? Yes. > As I understand maven, test will be executed using dependencies from the reactor, not from local repository. I don't get what is the point. Did you try to reproduce issue? Or should I provide full traces to you? > What am I missing? I see

Re: Maven. Issues with flatten plugin

> 2. run: > > `~/src/ignite/modules/spark> mvn install -U > -Plgpl,examples,scala,-clean-libs,-release,ml > -Dtest=org.apache.ignite.testsuites.IgniteRDDTestSuite > -Dmaven.javadoc.skip=true -DfailIfNoTests=false` > > It will execute OK, because maven uses pom.xml from source. Which pom.xml?

Re: Thin client: Java bindings

Igniters! Could you please help with the Java thin client code review: Documentation Code Thank you for the help. On Mon, Feb 5, 2018 at 5:45 PM, Alexey Kukushkin

Re: Transparent Data Encryption (TDE) in Apache Ignite

Hello, Igniters! I investigated the issue and wrote some details in a draft document [1]. I think we should made IEP for TDE because it is a big change and should be described in a single place, but not in a message conversation. Please, look it and write your thoughts. What is not

[GitHub] ignite pull request #3536: IGNITE-7717 Update discovery caches on topologies...

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

Re: Next Steps: GA Grid: Request to contribute GA library to Apache Ignite

Turik, I've made a review, please check it on the github, there is a question about pom files there. Also please update your branch from master. At this point we almost ready for merge. Regards, Yury -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-7857) Extend IgniteWalFlushMultiNodeFailoverAbstractSelfTest to cover MMAP mode

Ilya Lantukh created IGNITE-7857: Summary: Extend IgniteWalFlushMultiNodeFailoverAbstractSelfTest to cover MMAP mode Key: IGNITE-7857 URL: https://issues.apache.org/jira/browse/IGNITE-7857 Project:

[jira] [Created] (IGNITE-7856) ODBC: Support COPY command

Vladimir Ozerov created IGNITE-7856: --- Summary: ODBC: Support COPY command Key: IGNITE-7856 URL: https://issues.apache.org/jira/browse/IGNITE-7856 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-7855) ODBC: Supoprt streaming mode

Vladimir Ozerov created IGNITE-7855: --- Summary: ODBC: Supoprt streaming mode Key: IGNITE-7855 URL: https://issues.apache.org/jira/browse/IGNITE-7855 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-7854) Java thin client: add username/password authentication support

Vladimir Ozerov created IGNITE-7854: --- Summary: Java thin client: add username/password authentication support Key: IGNITE-7854 URL: https://issues.apache.org/jira/browse/IGNITE-7854 Project: Ignite

[jira] [Created] (IGNITE-7852) ODBC: Support username/password authentication

Vladimir Ozerov created IGNITE-7852: --- Summary: ODBC: Support username/password authentication Key: IGNITE-7852 URL: https://issues.apache.org/jira/browse/IGNITE-7852 Project: Ignite Issue

[jira] [Created] (IGNITE-7853) .NET thin client: supoprt username/password authentication

Vladimir Ozerov created IGNITE-7853: --- Summary: .NET thin client: supoprt username/password authentication Key: IGNITE-7853 URL: https://issues.apache.org/jira/browse/IGNITE-7853 Project: Ignite

[GitHub] ignite pull request #3586: IGNITE-7843: refresh index column ids on DROP COL...

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

Re: Maven. Issues with flatten plugin

I agree with Anton, especially with the following statement: >> Ignite should be assemblied using package phase, >> not install in case you want only to assembly it. Approach with "install" phase may lead to hidden issues in a development environment. On Thu, Mar 1, 2018 at 2:26 PM, Nikolay

Re: Maven. Issues with flatten plugin

> May be it will be enough to add a profile to parent pom.xml which activates on deploy stage only. I think it will be enough to solve my issue. > What pom.xml becomes flattened, what is removed from it and how it effects other modules of the same project? pom.xml that are installed to local

Re: Maven. Issues with flatten plugin

Nikolay, Sure, I think we have to create IEP "Assembly and Release cleanup and simplification". I see some issues can be attached to this IEP - Fabric word removal - Flatten plugin removal (in possible) - Ignite should be assemblied using package phase, not install in case you want only to

Re: Maven. Issues with flatten plugin

May be it will be enough to add a profile to parent pom.xml which activates on deploy stage only. Yet, I still do not get a mechanism that causes a problem. What pom.xml becomes flattened, what is removed from it and how it effects other modules of the same project? > On 1 Mar 2018, at

Re: Maven. Issues with flatten plugin

Andrey, thank you. If there are no other objections I will create ticket for pom structure refactoring. Anton, can you help me with it as an Ignite Release Manager? 2018-03-01 13:45 GMT+03:00 Andrey Novikov : > Nikolay, > > I think it can be removed, if parent-pom will be

Re: Maven. Issues with flatten plugin

Nikolay, I think it can be removed, if parent-pom will be installed(deployed). On Thu, Mar 1, 2018 at 5:05 PM, Nikolay Izhikov wrote: > Hello, Andrey. > > Thanks for an answer. > >> As I remember we use `flatten-maven-plugin` for flattening and removing >> parent

Re: Maven. Issues with flatten plugin

Hello, Andrey. Thanks for an answer. > As I remember we use `flatten-maven-plugin` for flattening and removing > parent relationship in deployed artifacts So we need it only in `release` profile? I found some earlier discussion about plugin [1] > in first versions of build, version was

Re: Maven. Issues with flatten plugin

Nikolay, As I remember we use `flatten-maven-plugin` for flattening and removing parent relationship in deployed artifacts (parent pom does not deploy to repository and in first versions of build, version was stored in variable in parent pom) On Thu, Mar 1, 2018 at 4:57 PM, Nikolay Izhikov

Re: Maven. Issues with flatten plugin

Hello, Petr. > Can you describe your problem In Ignite, maven doesn't include transitive dependencies to test classpath. So we have enlist all dependencies in project pom.xml. > desired behaviour All I want is default maven behavior. Please, take a look at pom.xml [1] from line 144. There is

Re: Nodes which started in separate JVM couldn't stop properly (in tests)

Thank you, Dmitry! I'll join this review soon. On Thu, Mar 1, 2018 at 12:07 PM, Dmitry Pavlov wrote: > Hi Vyacheslav, > > I will take a look, but first of all I am going to review > https://reviews.ignite.apache.org/ignite/review/IGNT-CR-502 - it is impact > change in

Re: Nodes which started in separate JVM couldn't stop properly (in tests)

Hi Vyacheslav, I will take a look, but first of all I am going to review https://reviews.ignite.apache.org/ignite/review/IGNT-CR-502 - it is impact change in testing framework. Hope you also will join to this review . Sincerely, Dmitiry Pavlov чт, 1 мар. 2018 г. в 11:13, Vyacheslav Daradur

Re: Maven. Issues with flatten plugin

Nikolay, Can you describe your problem and desired behaviour more thoroughly, please? > On 28 Feb 2018, at 21:16, Nikolay Izhikov wrote: > > Hello, Igniters. > > We have `flatten-maven-plugin` in `parent/pom.xml` [1] > As far as I can understand it minimize pom.xml

[GitHub] ignite pull request #3451: IGNITE-7366 Service reassignment with merge excha...

GitHub user xtern reopened a pull request: https://github.com/apache/ignite/pull/3451 IGNITE-7366 Service reassignment with merge exchanges. You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-7366 Alternatively

[GitHub] ignite pull request #3451: Service reassign with merge exchanges (TC run).

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

Re: Nodes which started in separate JVM couldn't stop properly (in tests)

Hi, Dmitry, could you please review it, because you are one of the most experienced people in the testing framework. Please see comment in Jira, because it is in pretty-format there. On Thu, Feb 22, 2018 at 11:56 AM, Vyacheslav Daradur wrote: > Hi Igniters! > > I have