Re: ALTER TABLE command support

Alex, There are several complex things here: 1) DROP TABLE will require modification of data. Effectively, we have to rebuild all binary objects in our cache. And the key question - how to make this process efficient. Without it the following will fail: INSERT INTO Person(id, salary) VALUES (1,

[jira] [Created] (IGNITE-5367) Web console: Sql page fixes.

Vasiliy Sisko created IGNITE-5367: - Summary: Web console: Sql page fixes. Key: IGNITE-5367 URL: https://issues.apache.org/jira/browse/IGNITE-5367 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5366) Web Console: user notifications

Ilya Borisov created IGNITE-5366: Summary: Web Console: user notifications Key: IGNITE-5366 URL: https://issues.apache.org/jira/browse/IGNITE-5366 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #2054: IGNITE-5328 Added CREATE TABLE params

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2054 IGNITE-5328 Added CREATE TABLE params You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5328 Alternatively

Re: ALTER TABLE command support

Hi guys, To my knowledge, our binary format is currently resilient to adding/removing fields of individual objects while having those objects logically belonging to the same value type - thanks to all efforts with binary resolvers and stable field sorting. Thus, ALTER TABLE implemented as

WAL fsync mode to the public API

Alex G., Igniters, Why do we hide WAL fsync modes in the internals of FileWriteAheadLogManager? private enum Mode { NONE, LOG_ONLY, /** * Write is performed periodically, initiated by background thread, * calls to {@link

Re: contention on DataStructure creation/removing

Won't it be confusing from a user stand point to have multiple data structures with the same name? Also, what is the performance impact of this change? D. On Wed, May 31, 2017 at 8:23 AM, Semyon Boikov wrote: > Hi Mikhail, > > As far as I remember for some reason we

Re: Persistent Store Stabilization for release

Thanks Denis. I also would like to encourage to post all the stabilization updates for the donated branch here. This will help the community to get familiar with the new code and functionality. In addition, everyone in the community should feel free to peruse through the code in this branch and

Re: Summary of SQL changes in 2.1

Vladmir, Thanks for the detailed email. My comments are inline... On Wed, May 31, 2017 at 11:21 AM, Vladimir Ozerov wrote: > Folks, > > Let me summarize all recent changes to our SQL engine which are important > from user perspective. Please think of them and let me know

Re: Persistent Distributed Store Metrics

Denis, I do agree, the concept of virtual memory may work. I will start another discussion thread on that. We should extensively javadoc all these interfaces. The current one-liner javadoc documentation is not enough. Also, I would like to make a small correction to the MemoryMetrics interface,

Re: ALTER TABLE command support

Agree. The gradual approach is the way to go for us. — Denis > On May 31, 2017, at 1:20 PM, Dmitriy Setrakyan wrote: > > I think a fully functional ALTER TABLE command may be hard to implement, as > it includes changes of columns, types, constraints, etc... We should

Re: ALTER TABLE command support

I think a fully functional ALTER TABLE command may be hard to implement, as it includes changes of columns, types, constraints, etc... We should take a gradual approach here and implement this command by phases. I would propose that in the first phase we simply add the capability to add and

Re: ALTER TABLE command support

Denis There's a few key points how we plan to process ALTER operations (online, locking mode). Take a look [1] [1] https://dev.mysql.com/doc/refman/5.6/en/innodb-create-index-overview.html On Wed, May 31, 2017 at 9:52 PM, Denis Magda wrote: > Sergi, Vovan, Alexander P., >

ALTER TABLE command support

Sergi, Vovan, Alexander P., It’s great that we added CREATE/DROP index commands support to Ignite. As the next step, I think we need to move forward and plan to add ALTER TABLE command to the list. The reason we should have this command is simple. If a user adds a new field to Person class

[GitHub] ignite pull request #1989: IGNITE-4724: SQL: corrected result type for AVG()

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1989 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

nested SQL sub-queries with non-collocated joins

Igniters (specifically Sergi), It has come to my attention today that nested sub-select statements, when used in combination with non-collocated joins do not work properly in Ignite. So a query like this, where A, B, and C are all stored in Partitioned caches and are **not** collocated at all,

Summary of SQL changes in 2.1

Folks, Let me summarize all recent changes to our SQL engine which are important from user perspective. Please think of them and let me know if you have any objection and thoughts on how to improve them. 1) Default "PUBLIC" schema added. It always exists and cannot be dropped. Many caches can

Re: Cache.getAll can return partially commited results. IGNITE-4809

Aleksey, Generally, this decision cannot be made on a single node because a transaction may affect multiple nodes, and one node may have already committed the transaction and the other - not. There is a dependant ticket in the ticket you are currently working on which will cover all the caes.

[jira] [Created] (IGNITE-5365) Build release artifacts once and use them for all editions

Anton Vinogradov created IGNITE-5365: Summary: Build release artifacts once and use them for all editions Key: IGNITE-5365 URL: https://issues.apache.org/jira/browse/IGNITE-5365 Project: Ignite

Re: Cache.getAll can return partially commited results. IGNITE-4809

one possible solution is to lock entry reading section while userCommit() method is executing. ср, 31 мая 2017 г., 16:52 ALEKSEY KUZNETSOV : > Hi, Igntrs! > When the first writer thread has commited values and cache entries are > getting updated with this new values,

[GitHub] ignite pull request #2053: IGNITE-5364 Remove contention on DataStructure cr...

GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/2053 IGNITE-5364 Remove contention on DataStructure creation or removing All DSs are stored in one Map which itself is stored in utilityCache, this makes high contention on DS creation or removing,

[GitHub] ignite pull request #2052: IGNITE-3795: Added C++ cache query tests with CUR...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2052 IGNITE-3795: Added C++ cache query tests with CURDATE() You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3795

[jira] [Created] (IGNITE-5364) Remove contention on DS creation or removing

Mikhail Cherkasov created IGNITE-5364: - Summary: Remove contention on DS creation or removing Key: IGNITE-5364 URL: https://issues.apache.org/jira/browse/IGNITE-5364 Project: Ignite

[jira] [Created] (IGNITE-5363) Exception in logs after starting cluster in inactive mode and subsequent activation

Sergey Chugunov created IGNITE-5363: --- Summary: Exception in logs after starting cluster in inactive mode and subsequent activation Key: IGNITE-5363 URL: https://issues.apache.org/jira/browse/IGNITE-5363

[GitHub] ignite pull request #2037: IGNITE-5161: Implemented compute example for C++

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/2037 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2047: IGNITE-5154: Added RemoteFilter to C++ ContinuosQ...

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/2047 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2051: Ignite 1.9.3 Release

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

place for printing info about partition distribution

Hello guys! I want to discuss and suggest some format and place for pinting info about partition distribution to log from issue https://issues.apache.org/jira/browse/IGNITE-4756 What do you think about it ? Issue is about RendezvousAffinityFunction and FairAffinityFunction classes. Vadim

Re: contention on DataStructure creation/removing

Hi Mikhail, As far as I remember for some reason we wanted to guarantee that all data structures have unique names. But now I don't see why this can be needed and it seems we do not need this data structures map at all, if nobody have objection I think you can implement suggested change. Thanks!

[GitHub] ignite pull request #2050: IGNITE-5255 JDBC Driver: support DML

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2050 IGNITE-5255 JDBC Driver: support DML You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5255

[jira] [Created] (IGNITE-5362) Improve test coverage of SQL schema-related changes

Vladimir Ozerov created IGNITE-5362: --- Summary: Improve test coverage of SQL schema-related changes Key: IGNITE-5362 URL: https://issues.apache.org/jira/browse/IGNITE-5362 Project: Ignite

[jira] [Created] (IGNITE-5361) Query for string field represented as CHAR SQL type in underlying database doesn't retrieve entires that were loaded with CacheJdbcPojoStore

Andrey Gura created IGNITE-5361: --- Summary: Query for string field represented as CHAR SQL type in underlying database doesn't retrieve entires that were loaded with CacheJdbcPojoStore Key: IGNITE-5361 URL:

[GitHub] ignite pull request #2049: IGNITE-5243

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

Contributor access

Dear Ignite community, Can you please grant me (lexa) contributor access, so that I can assign Ignite Jira issues to myself ? Best Regards Aleksey Chetaev. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Contributor-access-tp18242.html Sent from the

Cache.getAll can return partially commited results. IGNITE-4809

Hi, Igntrs! When the first writer thread has commited values and cache entries are getting updated with this new values, another thread is getting partially assigned values through the cache.getAll(keys) should this method wait for all newly updated entries to finish , or should it throw the

[GitHub] ignite pull request #2048: IGNITE-5358 .NET: Fix nullable enum field handlin...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2048 IGNITE-5358 .NET: Fix nullable enum field handling in binary objects You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite

Re: Grant contributors access

Done! Feel free to proceed! --Yakov 2017-05-31 12:07 GMT+03:00 Алексей Четаев : > Dear Ignite community, > > Can you please grant me (lexa) contributor access, so that I can > assign Ignite Jira issues to myself ? > > Best Regards > Aleksey Chetaev. >

[GitHub] ignite pull request #2038: IGNITE-5337: Renamed C++ example executables for ...

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/2038 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-5360) Validate SQL configuration state from discovery thread

Vladimir Ozerov created IGNITE-5360: --- Summary: Validate SQL configuration state from discovery thread Key: IGNITE-5360 URL: https://issues.apache.org/jira/browse/IGNITE-5360 Project: Ignite

Grant contributors access

Dear Ignite community, Can you please grant me (lexa) contributor access, so that I can assign Ignite Jira issues to myself ? Best Regards Aleksey Chetaev.

[jira] [Created] (IGNITE-5359) SQL subquery with aggregates return wrong results.

Andrew Mashenkov created IGNITE-5359: Summary: SQL subquery with aggregates return wrong results. Key: IGNITE-5359 URL: https://issues.apache.org/jira/browse/IGNITE-5359 Project: Ignite

[jira] [Created] (IGNITE-5358) .NET: Nullable enum field in binary object causes type cast exception

Pavel Tupitsyn created IGNITE-5358: -- Summary: .NET: Nullable enum field in binary object causes type cast exception Key: IGNITE-5358 URL: https://issues.apache.org/jira/browse/IGNITE-5358 Project:

Re: contention on DataStructure creation/removing

Mikhail, Seems, This can solve "slow reentrantLock" issue, at least at creation stage. On Wed, May 31, 2017 at 3:04 PM, Mikhail Cherkasov wrote: > Hi all, > > All DataStructures are stored in one Map which itself is stored in > utilityCache, this makes high contention

contention on DataStructure creation/removing

Hi all, All DataStructures are stored in one Map which itself is stored in utilityCache, this makes high contention on DS creation or removing, it requires to acquire Map's lock and manipulation with the Map under the lock. So all threads in cluster should wait for this lock to create or remove

[GitHub] ignite pull request #2046: Removed DS map, all DS is added to utilityCache d...

GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/2046 Removed DS map, all DS is added to utilityCache directly All DSs are stored in one Map which itself is stored in utilityCache, this makes high contention on DS creation or removing, it requires

[GitHub] ignite pull request #2044: IGNITE-5320

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/2044 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2045: MemoryPolicyConfiguration.rateTimeInterval proper...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2045 MemoryPolicyConfiguration.rateTimeInterval property changed its type to long You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-5357) Replicated cache reads load balancing.

Alexei Scherbakov created IGNITE-5357: - Summary: Replicated cache reads load balancing. Key: IGNITE-5357 URL: https://issues.apache.org/jira/browse/IGNITE-5357 Project: Ignite Issue

[jira] [Created] (IGNITE-5356) .NET: Peer deployment does not load runtime dependencies

Pavel Tupitsyn created IGNITE-5356: -- Summary: .NET: Peer deployment does not load runtime dependencies Key: IGNITE-5356 URL: https://issues.apache.org/jira/browse/IGNITE-5356 Project: Ignite

[GitHub] ignite pull request #2044: IGNITE-5320

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

[GitHub] ignite pull request #2042: IGNITE-5354 .NET: Fix command line args preferenc...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2042 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2043: IGNITE-5097: writing arrays length in varint enco...

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/2043 IGNITE-5097: writing arrays length in varint encoding was implemented You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite

Re: IgniteCompute async methods do not return ComputeTaskFuture

Here is the scenario we cannot support for now. User cannot cancel tasks after master node is restarted. Of course, we need to restore IgniteCompute.cancelTask(sesId) first. I am against changing closures execution mechanics. I would better simplify and optimize task execution. This way, both

[jira] [Created] (IGNITE-5355) Create task with release tools

Aleksey Chetaev created IGNITE-5355: --- Summary: Create task with release tools Key: IGNITE-5355 URL: https://issues.apache.org/jira/browse/IGNITE-5355 Project: Ignite Issue Type: Task

Re: New thin JDBC driver

I think I will add completely *new *top-level bean "SqlConfiguration". For now it will contain: 1) Long query warning timeout (it doesn't make sense anymore on cache configuration) 2) SQL function classes (also move from cache config) 3) Listener parameters: host, port, max cursors On Thu, May

[GitHub] ignite pull request #2042: IGNITE-5354 .NET: Fix command line args preferenc...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2042 IGNITE-5354 .NET: Fix command line args preference over config file You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite

[jira] [Created] (IGNITE-5354) .NET: ConfigSectionName can not be overridden from command line

Pavel Tupitsyn created IGNITE-5354: -- Summary: .NET: ConfigSectionName can not be overridden from command line Key: IGNITE-5354 URL: https://issues.apache.org/jira/browse/IGNITE-5354 Project: Ignite

[GitHub] ignite pull request #1979: IGNITE-5054

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1979 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2024: IGNITE-5317

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/2024 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2039: IGNITE-5273 .NET: MemoryMetrics API improvements ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2039 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1996: Ignite-5242

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1996 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-5353) .NET: Pure SQL & DDL example

Pavel Tupitsyn created IGNITE-5353: -- Summary: .NET: Pure SQL & DDL example Key: IGNITE-5353 URL: https://issues.apache.org/jira/browse/IGNITE-5353 Project: Ignite Issue Type: Improvement