[GitHub] ignite pull request #2622: Ignite-1.9.6.b3

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2622 Ignite-1.9.6.b3 for test purposes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.9.6.b3 Alternatively you

Re: Monitoring of active transactions

Hello, Ilya. Great! Thanks! Can I extend your idea a bit? I think it be very useful monitor all-user provided listeners and callbacks also. To handle following scenarios: 1а. User starts a job with ExecutorService, IgniteCompute or similar. 1b. User creates ContinuousQuery with

Monitoring of active transactions

Igniters, According to our current design and implementation, unclosed transaction or unreleased lock can hang ignite cluster forever. This is logical, and with correct usage of those mechanics such issue should never happen, in real world developers can make mistakes and leave transaction open.

[jira] [Created] (IGNITE-6312) Link to unexisted URL on ExecutorService page

Nikolay Izhikov created IGNITE-6312: --- Summary: Link to unexisted URL on ExecutorService page Key: IGNITE-6312 URL: https://issues.apache.org/jira/browse/IGNITE-6312 Project: Ignite Issue

[GitHub] ignite pull request #2623: Ignite-1.9.7

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

[GitHub] ignite pull request #2624: IGNITE-6030 Persistence per memoryPolicy (first w...

GitHub user kdudkov opened a pull request: https://github.com/apache/ignite/pull/2624 IGNITE-6030 Persistence per memoryPolicy (first working test) You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Monitoring of active transactions

Hi Ilya, I'm definitely +1 for including the utility in the product. Perfect contribution. Sincerely, Dmitriy Pavlov пт, 8 сент. 2017 г. в 14:28, Ilya Lantukh : > Igniters, > > According to our current design and implementation, unclosed transaction or > unreleased lock

[jira] [Created] (IGNITE-6313) transaction hangs while node left cluster

Stanilovsky Evgeny created IGNITE-6313: -- Summary: transaction hangs while node left cluster Key: IGNITE-6313 URL: https://issues.apache.org/jira/browse/IGNITE-6313 Project: Ignite Issue

[jira] [Created] (IGNITE-6314) Fix alter table tests failures

Sergey Kalashnikov created IGNITE-6314: -- Summary: Fix alter table tests failures Key: IGNITE-6314 URL: https://issues.apache.org/jira/browse/IGNITE-6314 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6315) Exception during DistributedRegressionExample (ML)

Ilya Suntsov created IGNITE-6315: Summary: Exception during DistributedRegressionExample (ML) Key: IGNITE-6315 URL: https://issues.apache.org/jira/browse/IGNITE-6315 Project: Ignite Issue

Add ANTLR dependency (BSD!) to Apache Ignite

Igniters, We are evaluating ANTLR [1] as a parser generator for our SQL engine [2]. At first glance it looks very good, we already able to parse certain SQL commands with it. If implemented, it would greatly improve usability of our SQL engine. However, it goes under BSD license and require one

[jira] [Created] (IGNITE-6310) BaselineTopology versioning

Sergey Chugunov created IGNITE-6310: --- Summary: BaselineTopology versioning Key: IGNITE-6310 URL: https://issues.apache.org/jira/browse/IGNITE-6310 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-6307) If getAll() fails with NPE, onHeap entry is not removed, for local cache

Dmitriy Govorukhin created IGNITE-6307: -- Summary: If getAll() fails with NPE, onHeap entry is not removed, for local cache Key: IGNITE-6307 URL: https://issues.apache.org/jira/browse/IGNITE-6307

[GitHub] ignite pull request #2621: IGNITE-6070 Ensure that Web Session RequestWrappe...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/2621 IGNITE-6070 Ensure that Web Session RequestWrapper considers its sess… …ions valid. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6311) Initial BaselineTopology is defined with static configuration

Sergey Chugunov created IGNITE-6311: --- Summary: Initial BaselineTopology is defined with static configuration Key: IGNITE-6311 URL: https://issues.apache.org/jira/browse/IGNITE-6311 Project: Ignite

[GitHub] ignite pull request #2260: IGNITE-5718: Forcible node drop makes cluster ins...

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

[GitHub] ignite pull request #1326: Ignite 3558

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

[jira] [Created] (IGNITE-6308) BaselineTopology is created on first cluster activation

Sergey Chugunov created IGNITE-6308: --- Summary: BaselineTopology is created on first cluster activation Key: IGNITE-6308 URL: https://issues.apache.org/jira/browse/IGNITE-6308 Project: Ignite

[GitHub] ignite pull request #2403: for test purposes.

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

[jira] [Created] (IGNITE-6309) .NET: Thin client: Do not buffer entire socket response

Pavel Tupitsyn created IGNITE-6309: -- Summary: .NET: Thin client: Do not buffer entire socket response Key: IGNITE-6309 URL: https://issues.apache.org/jira/browse/IGNITE-6309 Project: Ignite

[GitHub] ignite pull request #2625: IGNITE-6244 .NET: Thin client: ScanQuery

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

[GitHub] ignite pull request #2626: IGNITE-5549 : Fixed situation when mvcc pending q...

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2626 IGNITE-5549 : Fixed situation when mvcc pending queue wasn't cleared. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-6322) NPE after removing persistent store directory

Pavel Tupitsyn created IGNITE-6322: -- Summary: NPE after removing persistent store directory Key: IGNITE-6322 URL: https://issues.apache.org/jira/browse/IGNITE-6322 Project: Ignite Issue

[jira] [Created] (IGNITE-6316) SQL: Add ALTER TABLE tests with persistence

Vladimir Ozerov created IGNITE-6316: --- Summary: SQL: Add ALTER TABLE tests with persistence Key: IGNITE-6316 URL: https://issues.apache.org/jira/browse/IGNITE-6316 Project: Ignite Issue

[jira] [Created] (IGNITE-6320) SQL: ANTLR performance assessment

Vladimir Ozerov created IGNITE-6320: --- Summary: SQL: ANTLR performance assessment Key: IGNITE-6320 URL: https://issues.apache.org/jira/browse/IGNITE-6320 Project: Ignite Issue Type: Task

Re: Monitoring of active transactions

Ilya, We extremely need this! Txs and Locks info should be collected on each cluster hang. We already have an issue related to this problem - https://issues.apache.org/jira/browse/IGNITE-4937 Nikolay, Good point, but, seems you should start separate thread to discuss this. On Fri, Sep 8, 2017

[jira] [Created] (IGNITE-6319) SQL: implement server-side DML for lazy mode

Vladimir Ozerov created IGNITE-6319: --- Summary: SQL: implement server-side DML for lazy mode Key: IGNITE-6319 URL: https://issues.apache.org/jira/browse/IGNITE-6319 Project: Ignite Issue

[jira] [Created] (IGNITE-6321) Nodes joining to active cluster remain in inactive state

Sergey Chugunov created IGNITE-6321: --- Summary: Nodes joining to active cluster remain in inactive state Key: IGNITE-6321 URL: https://issues.apache.org/jira/browse/IGNITE-6321 Project: Ignite

[jira] [Created] (IGNITE-6317) JDBC thick driver: SQLSTATE error codes

Vladimir Ozerov created IGNITE-6317: --- Summary: JDBC thick driver: SQLSTATE error codes Key: IGNITE-6317 URL: https://issues.apache.org/jira/browse/IGNITE-6317 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6318) SQL: Make sure that QueryTypeDescriptorImpl is used in thread-safe manner

Vladimir Ozerov created IGNITE-6318: --- Summary: SQL: Make sure that QueryTypeDescriptorImpl is used in thread-safe manner Key: IGNITE-6318 URL: https://issues.apache.org/jira/browse/IGNITE-6318

Re: Add ANTLR dependency (BSD!) to Apache Ignite

Vladimir, Yes, we can include the lib in our project. ANTLR is “BSD 3-clause license” [1] that is compliant with Apache 2.0 [2]. [1] https://github.com/antlr/antlr4/blob/master/LICENSE.txt [2]

Fwd: Cassandra failing to ReadThrough using Cache.get(key) without preloading

Hi Igor, Could you check this message from user list? I can't find any reasons why readThrough doesn't work with Cassandra here Thanks, Evgenii -- Forwarded message -- From: Kenan Dalley Date: 2017-08-31 17:14 GMT+03:00 Subject: Re: Cassandra failing to

Re: Ignite Benchmarking page on readme.io

Thanks. Here is a direct link on the new page about Ignite Benchmarking(hidden for now): https://apacheignite.readme.io/v2.1/docs/perfomance-tests. Please review. Mostly it was aggregated from the information in the repo 07.09.2017, 20:57, "Dmitriy Setrakyan" : >

[jira] [Created] (IGNITE-6323) Ignite node not stopping after segmentation

Mikhail Cherkasov created IGNITE-6323: - Summary: Ignite node not stopping after segmentation Key: IGNITE-6323 URL: https://issues.apache.org/jira/browse/IGNITE-6323 Project: Ignite Issue

Re: Logging documentation

Unbelievable! So many years went by and finally we got this documentation ready. Thanks a lot Prachi! — Denis > On Sep 8, 2017, at 9:48 AM, Prachi Garg wrote: > > Hello Igniters, > > I see a lot of questions about logging in Ignite . Here is the documentation- >

Re: Add ANTLR dependency (BSD!) to Apache Ignite

Vova, license-wise it is OK, but I do not like adding the dependency. Right now we have H2 doing parsing for us. Why would ANTLR be better? What happens when we potentially notice a performance issue or any other issue in ANTLR under load? Can we try doing parsing ourselves instead of adding a

Re: sql documentation

Igniter (especially those who are willing to work on the new SQL doc), The doc for SQL capabilities has been set up. Copy pasted all the SQL materials we have there: https://apacheignite-sql.readme.io/docs Sergey P., feel free to start reworking the

Re: sql documentation

Denis, Can you please add me as an admin to that site? D. On Fri, Sep 8, 2017 at 3:23 PM, Denis Magda wrote: > Igniter (especially those who are willing to work on the new SQL doc), > > The doc for SQL capabilities has been set up. Copy pasted all the SQL > materials we

about document missing

Hi The documentation below is missing in the 2.1.0 version. I hope someone in the community will help to confirm it: https://apacheignite.readme.io/v2.0/docs/sliding-windows https://apacheignite.readme.io/v2.0/docs/streaming-example

Re: sql documentation

Please check you inbox. — Denis > On Sep 8, 2017, at 3:38 PM, Dmitriy Setrakyan wrote: > > Denis, > > Can you please add me as an admin to that site? > > D. > > On Fri, Sep 8, 2017 at 3:23 PM, Denis Magda wrote: > >> Igniter (especially those who

[jira] [Created] (IGNITE-6306) Visor CMD: Improvement of alert command

Vasiliy Sisko created IGNITE-6306: - Summary: Visor CMD: Improvement of alert command Key: IGNITE-6306 URL: https://issues.apache.org/jira/browse/IGNITE-6306 Project: Ignite Issue Type: Bug

Re: Logging documentation

Great! I think the next task should be to explain expiration vs eviction. I am seeing too many questions on it as well. At this point, I am also confused about how it really works. D. On Fri, Sep 8, 2017 at 10:18 AM, Denis Magda wrote: > Unbelievable! So many years went by