[jira] [Created] (IGNITE-7275) Admin panel: Grant\Revoke menu item text doesn't change

Alexander Kalinin created IGNITE-7275: - Summary: Admin panel: Grant\Revoke menu item text doesn't change Key: IGNITE-7275 URL: https://issues.apache.org/jira/browse/IGNITE-7275 Project: Ignite

[GitHub] ignite pull request #3267: IGNITE-6951 .NET: Support pointer serialization

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3267 IGNITE-6951 .NET: Support pointer serialization You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-6951 Alternatively

Re: List of running Continuous queries or CacheEntryListener per cache or node

Crossposting to devlist. Hi Igniters! It's might be a nice feature to have - get list of registered continuous queries with ability to deregister them. What do you think? Thanks! -Dmitry 20.12.2017 16:59, fefe пишет: For sanity checks or tests. I want to be sure that I haven't forgot to

Re: Create cache using thin protocol

Hi Prachi, Yes, you have to provide full configuration. The error is caused by incomplete request message. Alternatively, define cache templates on server (configs with * in them) and then use OP_CACHE_CREATE_WITH_NAME from thin client. Thanks, Pavel On Thu, Dec 21, 2017 at 3:47 AM, Prachi

Re: IGNITE-6853: Cassandra cache store does not clean prepared statements cache when remove old cassandra session

Hi Jason, Thanks for fixing the bug! Please assign the ticket on yourself, move it to “PATCH AVAILABLE” state and run Cassandra specific tests on TeamCity. More on this can be found here: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-SubmittingforReview

IGNITE-6853: Cassandra cache store does not clean prepared statements cache when remove old cassandra session

Hi Igniters, I've got a PR to resolve this JIRA available: https://issues.apache.org/jira/browse/IGNITE-6853 https://github.com/apache/ignite/pull/3088 The JIRA was tagged previously with fix version = 2.4 May I know what is the process to move things forward? (The PR has been created 3

Re: Transaction classes naming

for renaming +1 > 21 дек. 2017 г., в 5:25, Dmitriy Setrakyan написал(а): > > Will this renaming introduce any issues with supporting previous versions? > >> On Wed, Dec 20, 2017 at 9:10 AM, Yakov Zhdanov wrote: >> >> How about we explain it in

[GitHub] ignite pull request #3266: IGNITE-7272

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

Re: Hello Ignite

Hi Stan, Please tell me your JIRA id and I’ll add you to the contributors list. 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:

[jira] [Created] (IGNITE-7274) Web Agent: Support multiple statements on Queries screen.

Alexey Kuznetsov created IGNITE-7274: Summary: Web Agent: Support multiple statements on Queries screen. Key: IGNITE-7274 URL: https://issues.apache.org/jira/browse/IGNITE-7274 Project: Ignite

Re: Time and scope for Apache Ignite 2.4

Hi, Denis. Yes, we collaborated with Yuri and are currently waiting for Ignite Tests run results (though I’ll be able to start full comparison run only on weekend because of extremely high TC load) to be sure that 1) I did not break overall build and 2) building and testing on Java 8 produces

Hello Ignite

Hello Ignite Devs, My name is Stan and I want to contribute to the Apache Ignite project. I’d like to start by fixing https://issues.apache.org/jira/browse/IGNITE-7217. I understand that I need additional JIRA access rights to assign the IGNITE-7217 to myself. Could someone please grant me

[jira] [Created] (IGNITE-7273) Web console: Profile in "main work tab" doesn't see changes of Profile made in another tab

Pavel Konstantinov created IGNITE-7273: -- Summary: Web console: Profile in "main work tab" doesn't see changes of Profile made in another tab Key: IGNITE-7273 URL:

Re: Transaction classes naming

Will this renaming introduce any issues with supporting previous versions? On Wed, Dec 20, 2017 at 9:10 AM, Yakov Zhdanov wrote: > How about we explain it in javadocs and properly document on wiki? Guys, I > would do this at some point when there is no another bigger issue

Re: Suppressing "development" warning

Sounds good, markers should work. On Wed, Dec 20, 2017 at 1:00 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Dmitry, > > WARNING_DEV_ONLY actually sounds like a custom *level* name. Unfortunately, > this is not possible because most of the loggers do not support this. > > I

Create cache using thin protocol

Pavel, I tried to create a cache with configuration, using the thin protocol. 1. Do I need to provide every configuration as mentioned in the wiki, or I can just provide a few and the rest can be default? 2. Using the below code: DataOutputStream out = new

[GitHub] ignite pull request #3266: IGNITE-7272

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

[jira] [Created] (IGNITE-7272) SQL TX: incorrect row MVCC version override during CREATE INDEX

Vladimir Ozerov created IGNITE-7272: --- Summary: SQL TX: incorrect row MVCC version override during CREATE INDEX Key: IGNITE-7272 URL: https://issues.apache.org/jira/browse/IGNITE-7272 Project:

Re: Suppressing "development" warning

Dmitry, WARNING_DEV_ONLY actually sounds like a custom *level* name. Unfortunately, this is not possible because most of the loggers do not support this. I also don't like having special category for such warnings at least for these reasons: - Category does not defines severity of log statement,

Re: Time and scope for Apache Ignite 2.4

Please ping me or file a ticket following these rules [1] when this happens so that I could update this documentation page: https://apacheignite.readme.io/docs/memory-metrics [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document — Denis > On Dec 20, 2017, at 12:56 PM, Andrey

Re: Time and scope for Apache Ignite 2.4

Thanks, Denis! I hope I'll finish the task on memory metrics in a couple of days. 2017-12-20 23:28 GMT+03:00 Denis Magda : > Andrey K., excellent progress! Do you think you will finish the task by > the end of the year? > > Furthermore, I see you are working on Java 9

[jira] [Created] (IGNITE-7271) UPDATE and DELETE statements do not through thin JDBC work in MVCC mode

Vladimir Ozerov created IGNITE-7271: --- Summary: UPDATE and DELETE statements do not through thin JDBC work in MVCC mode Key: IGNITE-7271 URL: https://issues.apache.org/jira/browse/IGNITE-7271

Re: Time and scope for Apache Ignite 2.4

Andrey K., excellent progress! Do you think you will finish the task by the end of the year? Furthermore, I see you are working on Java 9 specific tasks: https://issues.apache.org/jira/browse/IGNITE-6728 Is everything alright there? If you

Re: Time and scope for Apache Ignite 2.4

Hi Peter, Sorry for confusion, yes, I meant using Java 8 by default in Ignite. Labeled the Java 8 ticket with “important” and now it appears in the required tickets list: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4#ApacheIgnite2.4-RequiredTickets As I see Yuri

Re: Removing "fabric" from Ignite binary package name

Petr, thanks, such a swift turnaround! Have you found the one who can asses and review the changes? Maintainers label might be helpful. Just ping them directly: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewProcessandMaintainers

[jira] [Created] (IGNITE-7270) .NET: Thin EntityFramework Second-Level Cache

Pavel Tupitsyn created IGNITE-7270: -- Summary: .NET: Thin EntityFramework Second-Level Cache Key: IGNITE-7270 URL: https://issues.apache.org/jira/browse/IGNITE-7270 Project: Ignite Issue

[jira] [Created] (IGNITE-7269) .NET: Thin ASP.NET Session State Store Provider

Pavel Tupitsyn created IGNITE-7269: -- Summary: .NET: Thin ASP.NET Session State Store Provider Key: IGNITE-7269 URL: https://issues.apache.org/jira/browse/IGNITE-7269 Project: Ignite Issue

[jira] [Created] (IGNITE-7268) SQL Tutorials Per Language

Denis Magda created IGNITE-7268: --- Summary: SQL Tutorials Per Language Key: IGNITE-7268 URL: https://issues.apache.org/jira/browse/IGNITE-7268 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #3265: BinaryMetadata should be merged on coordinator, o...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3265 BinaryMetadata should be merged on coordinator, otherwise there is a risk of data loss You can merge this pull request into a Git repository by running: $ git pull

Re: Transaction classes naming

How about we explain it in javadocs and properly document on wiki? Guys, I would do this at some point when there is no another bigger issue in Ignite =) --Yakov

Re: Transaction classes naming

Andrey, Good point. Even though it is not as confusing as near-remote naming, I agree that this should be fixed as well. 2017-12-20 18:59 GMT+03:00 Andrey Kuznetsov : > Alexey, > > And what do you think about 'Adapters' in transaction heirarchy? This term > looks really

[jira] [Created] (IGNITE-7267) Fix transactional inserts.

Igor Seliverstov created IGNITE-7267: Summary: Fix transactional inserts. Key: IGNITE-7267 URL: https://issues.apache.org/jira/browse/IGNITE-7267 Project: Ignite Issue Type: Bug

Re: Transaction classes naming

Alexey, And what do you think about 'Adapters' in transaction heirarchy? This term looks really obfuscating for new contributor, since in fact they are not adapters for something but abstract superclasses. 2017-12-20 18:18 GMT+03:00 Alexey Goncharuk : > Igniters, > >

Re: Transaction classes naming

As a person who tried to infer transactional behavior from listed classes, I completely agree. Also, I'd like to pay additional attention to: 1) IgniteTxAdapter#near method. It returns true both for GridNearTxLocal (where "near" means originating node) and GridNearTxRemote (where "near"

Re: Transaction classes naming

+1 On Wed, Dec 20, 2017 at 6:18 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Igniters, > > As I review transaction-related PRs and communicate with other fellow > Igniters, I realized that our transaction classes naming became > inconsistent and almost impossible to explain to a

Transaction classes naming

Igniters, As I review transaction-related PRs and communicate with other fellow Igniters, I realized that our transaction classes naming became inconsistent and almost impossible to explain to a new contributor. A few examples: 1) We have a GridNearTxLocal class, but Near in the name does not

[jira] [Created] (IGNITE-7266) SQL TX: Joins return duplicated result when MVCC is disabled

Vladimir Ozerov created IGNITE-7266: --- Summary: SQL TX: Joins return duplicated result when MVCC is disabled Key: IGNITE-7266 URL: https://issues.apache.org/jira/browse/IGNITE-7266 Project: Ignite

[GitHub] ignite pull request #3264: IGNITE-7165 Only cancel old rebalance future when...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3264 IGNITE-7165 Only cancel old rebalance future when new rebalance is non-trivial. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3255: Ignite gg 12015

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

[GitHub] ignite pull request #3263: IGNITE-6615 .NET: Thin client: XML configuration

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3263 IGNITE-6615 .NET: Thin client: XML configuration You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-6615 Alternatively

[GitHub] ignite pull request #3262: Ignite-1.7.18

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

[jira] [Created] (IGNITE-7265) BPlusTreeSelfTest.testIterateConcurrentPutRemove_1 fails

Vladimir Ozerov created IGNITE-7265: --- Summary: BPlusTreeSelfTest.testIterateConcurrentPutRemove_1 fails Key: IGNITE-7265 URL: https://issues.apache.org/jira/browse/IGNITE-7265 Project: Ignite

[jira] [Created] (IGNITE-7264) Caches with forward slash "/" in names cause problems for PDS

Ilya Kasnacheev created IGNITE-7264: --- Summary: Caches with forward slash "/" in names cause problems for PDS Key: IGNITE-7264 URL: https://issues.apache.org/jira/browse/IGNITE-7264 Project: Ignite

[jira] [Created] (IGNITE-7263) Daemon-mode Ignite node should not open client port (10800)

Alexey Popov created IGNITE-7263: Summary: Daemon-mode Ignite node should not open client port (10800) Key: IGNITE-7263 URL: https://issues.apache.org/jira/browse/IGNITE-7263 Project: Ignite

[jira] [Created] (IGNITE-7262) Most of clients get stuck with "Failed to wait for partition map ..." during load test with 500 logical caches

Ksenia Rybakova created IGNITE-7262: --- Summary: Most of clients get stuck with "Failed to wait for partition map ..." during load test with 500 logical caches Key: IGNITE-7262 URL:

[GitHub] ignite pull request #3261: Ignite 5804 ScanQuery transformer applies to firs...

GitHub user sk0x50 opened a pull request: https://github.com/apache/ignite/pull/3261 Ignite 5804 ScanQuery transformer applies to first results page only. You can merge this pull request into a Git repository by running: $ git pull https://github.com/sk0x50/ignite

[jira] [Created] (IGNITE-7261) SQL TX: SELECT and DML operations must share the same MVCC version

Vladimir Ozerov created IGNITE-7261: --- Summary: SQL TX: SELECT and DML operations must share the same MVCC version Key: IGNITE-7261 URL: https://issues.apache.org/jira/browse/IGNITE-7261 Project:

[GitHub] ignite pull request #3260: IGNITE-7197 Avoid NPE in services() by waiting on...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3260 IGNITE-7197 Avoid NPE in services() by waiting on latch You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3259: Ignite gg 12015m1

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3259 Ignite gg 12015m1 IGNITE-7197 Avoid NPE in services() by waiting on latch You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3258: IGNITE-5949: Added limited support for DDL ALTER ...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/3258 IGNITE-5949: Added limited support for DDL ALTER TABLE DROP COLUMN You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3207: IGNITE-7143: Fixed Decimal serialization issue

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

Re: Time and scope for Apache Ignite 2.4

Hi Denis, As for memory metrics, I'm fixing minor bugs now, and then we'll need some time for review. 2017-12-19 23:07 GMT+03:00 Denis Magda : > Igniters, > > It’s time to sync up on the progress of IMPORTANT tasks for 2.4: >

[GitHub] ignite pull request #3257: IGNITE-6803 UriDeployment, find resources fix.

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/3257 IGNITE-6803 UriDeployment, find resources fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6803-zstan

[jira] [Created] (IGNITE-7260) DDL needs to support DEFAULT value for ADD COLUMN operation

Taras Ledkov created IGNITE-7260: Summary: DDL needs to support DEFAULT value for ADD COLUMN operation Key: IGNITE-7260 URL: https://issues.apache.org/jira/browse/IGNITE-7260 Project: Ignite

[GitHub] ignite pull request #3256: IGNITE-5623: add support for DEFAULT value on CRE...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/3256 IGNITE-5623: add support for DEFAULT value on CREATE TABLE You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-7259) GridIndexRebuildSelfTest hangs

Vladimir Ozerov created IGNITE-7259: --- Summary: GridIndexRebuildSelfTest hangs Key: IGNITE-7259 URL: https://issues.apache.org/jira/browse/IGNITE-7259 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-7258) BinaryMetadata may be lost if node with outdated metadata becomes a coordinator

Sergey Chugunov created IGNITE-7258: --- Summary: BinaryMetadata may be lost if node with outdated metadata becomes a coordinator Key: IGNITE-7258 URL: https://issues.apache.org/jira/browse/IGNITE-7258

[jira] [Created] (IGNITE-7257) Web console: fix reconnection after change profile

Dmitriy Shabalin created IGNITE-7257: Summary: Web console: fix reconnection after change profile Key: IGNITE-7257 URL: https://issues.apache.org/jira/browse/IGNITE-7257 Project: Ignite

[GitHub] ignite pull request #3255: Ignite gg 12015

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3255 Ignite gg 12015 IGNITE-7197 Avoid NPE in services() by waiting on latch= You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3222: IGNITE-7197 Avoid NPE in serviced() by waiting on...

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

[jira] [Created] (IGNITE-7256) Web Console: Improve notification management.

Alexander Kalinin created IGNITE-7256: - Summary: Web Console: Improve notification management. Key: IGNITE-7256 URL: https://issues.apache.org/jira/browse/IGNITE-7256 Project: Ignite

[GitHub] ignite pull request #3254: Ignite 4191 mvcc enabled

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/3254 Ignite 4191 mvcc enabled You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4191-mvcc-enabled Alternatively you

[jira] [Created] (IGNITE-7255) SQL: Failed to execute explain via new "non-caches" API

Alexey Kuznetsov created IGNITE-7255: Summary: SQL: Failed to execute explain via new "non-caches" API Key: IGNITE-7255 URL: https://issues.apache.org/jira/browse/IGNITE-7255 Project: Ignite

[GitHub] ignite pull request #3186: Ignite 1.8.16

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

Re: Time and scope for Apache Ignite 2.4

Hi, Denis! What about switching to Java 8 by default? [1] I guess this task is inseparably connected to Java 7 support drop and Java 9 support introducing. [1] https://issues.apache.org/jira/browse/IGNITE-7203 > On 19 Dec 2017, at 23:07, Denis Magda wrote: > >

Re: Removing "fabric" from Ignite binary package name

Assigned myself — done the same work while preparing RPM package. But for fixing DEVNOTES.txt waiting for review and merge of IGNITE-7107 [1]. [1] https://issues.apache.org/jira/browse/IGNITE-7107 > On 19 Dec 2017, at 22:55, Denis Magda wrote: > > All the bids were