Oleg Ostanin created IGNITE-4822:
Summary: Editing default JVM options defined in Ignite-Yardstick
property files.
Key: IGNITE-4822
URL: https://issues.apache.org/jira/browse/IGNITE-4822
Project: Igni
Andrey Novikov created IGNITE-4821:
--
Summary: Web Console: Add EnforceJoinOrder option on Queries screen
Key: IGNITE-4821
URL: https://issues.apache.org/jira/browse/IGNITE-4821
Project: Ignite
Thanks, Vadim.
Merged the changes.
—
Denis
> On Mar 14, 2017, at 2:04 AM, Вадим Опольский wrote:
>
> Hello everybody!
>
> Denis, I prepared a pull-request and test executed successfully on TeamCity
> with awaiting time 500 milliseconds.
>
> Review it please - https://github.com/apache/ignite
Just a reminder.
The webinar will begin at 11:00 AM PST, March 15.
—
Denis
> On Mar 9, 2017, at 12:50 PM, Denis Magda wrote:
>
> Igniters,
>
> Let me invite you to join the next Apache Ignite webinar that will be fully
> dedicated to SQL Grid component:
> https://www.gridgain.com/company/ne
GitHub user alpert opened a pull request:
https://github.com/apache/ignite/pull/1623
Implement NoopEventStorageSpi and make default
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alpert/ignite ignite-4812
Alternatively you can
What is "consistent behavior"? Thread local in service just don't make
sense to me, it's a misuse. If you use API properly, you will not such
issues.
BTW, it's better to ask such questions on user list, not dev list. Please
do so for further questions.
-Val
On Tue, Mar 14, 2017 at 1:55 PM, 李玉珏@1
orchestrator is a custom thing. He is responsible for managing business
scenarios flows. Many nodes are involved in scenarios. They exchange data
and folow one another. If you acquinted with BPMN framework, so
orchestrator is like bpmn engine.
вт, 14 Мар 2017 г., 18:56 Sergi Vladykin :
> What is
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/1622
IGNITE-3575: CPP: Implemented remote filters for continuous queries
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite igni
What is Orchestrator for you? Is it a thing from Microsoft or your custom
in-house software?
Sergi
2017-03-14 18:00 GMT+03:00 ALEKSEY KUZNETSOV :
> Fine. Let's say we've got multiple servers which fulfills custom logic.
> This servers compound oriented graph (BPMN process) which controlled by
>
GitHub user ntikhonov opened a pull request:
https://github.com/apache/ignite/pull/1621
1.8.4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.8.4
Alternatively you can review and apply these chang
Fine. Let's say we've got multiple servers which fulfills custom logic.
This servers compound oriented graph (BPMN process) which controlled by
Orchestrator.
For instance, *server1 *creates *variable A *with value 1, persists it to
IGNITE cache and creates *variable B *and sends it to* server2. *T
Alexey Goncharuk created IGNITE-4820:
Summary: Implement parallel indexes for BPlusTree
Key: IGNITE-4820
URL: https://issues.apache.org/jira/browse/IGNITE-4820
Project: Ignite
Issue Type:
Ok, it is not a business case, it is your wrong solution for it.
Lets try again, what is the business case?
Sergi
2017-03-14 16:42 GMT+03:00 ALEKSEY KUZNETSOV :
> The case is the following, One starts transaction in one node, and commit
> this transaction in another jvm node(or rollback it remot
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/1620
Ignite 4535
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4535
Alternatively you can review and apply these c
Pavel Tupitsyn created IGNITE-4819:
--
Summary: Start .NET plugins before OnIgniteStart
Key: IGNITE-4819
URL: https://issues.apache.org/jira/browse/IGNITE-4819
Project: Ignite
Issue Type: Sub-
The case is the following, One starts transaction in one node, and commit
this transaction in another jvm node(or rollback it remotely).
вт, 14 мар. 2017 г. в 16:30, Sergi Vladykin :
> Because even if you make it work for some simplistic scenario, get ready to
> write many fault tolerance tests a
Because even if you make it work for some simplistic scenario, get ready to
write many fault tolerance tests and make sure that you TXs work gracefully
in all modes in case of crashes. Also make sure that we do not have any
performance drops after all your changes in existing benchmarks. All in all
Why wrong ? You know the better solution?
вт, 14 мар. 2017 г. в 15:46, Sergi Vladykin :
> Just serializing TX object and deserializing it on another node is
> meaningless, because other nodes participating in the TX have to know about
> the new coordinator. This will require protocol changes, we
This problem occurs in a stand-alone development environment, as well as
multiple node deployment environment.
I think it is reasonable to say that no matter where the service is
accessed, it is a different thread, which will ensure consistent behavior.
在 2017/3/13 23:52, Valentin Kulichenko 写道
Just serializing TX object and deserializing it on another node is
meaningless, because other nodes participating in the TX have to know about
the new coordinator. This will require protocol changes, we definitely will
have fault tolerance and performance issues. IMO the whole idea is wrong
and it
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/1619
IGNITE-4802
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/ignite ignite-4802
Alternatively you can review and apply these ch
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/1618
IGNITE-4716 .NET: Add IgniteUuid system type support
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-4716
Alternativ
I've added comments about IgniteConfiguration to JIRA ticket.
On Tue, Mar 14, 2017 at 2:06 PM, Alexey Kuznetsov
wrote:
> Maxim,
>
> I managed to review Web Console part in your PR.
> Looks good for me.
>
> But it seems that you also should delete following properties on
> IgniteConfiguration
>
Maxim,
I managed to review Web Console part in your PR.
Looks good for me.
But it seems that you also should delete following properties on
IgniteConfiguration
getClockSyncFrequency();
getClockSyncSamples();
Once you delete them - you should also delete them on WebConsole also.
P.S. do not
Okay, thank you.
2017-03-13 17:50 GMT+03:00 Valentin Kulichenko <
valentin.kuliche...@gmail.com>:
> This class can't be removed as it's part of public API. It's a convenience
> adapter that users can extend when using continuations.
>
> -Val
>
> On Mon, Mar 13, 2017 at 3:28 PM, Александр Меньшико
Pavel Tupitsyn created IGNITE-4818:
--
Summary: .NET DayOfWeek does not work as a LINQ parameter
Key: IGNITE-4818
URL: https://issues.apache.org/jira/browse/IGNITE-4818
Project: Ignite
Issue T
Aleksey,
Entry processor is always executed on the primary node and (sometimes) on
backup nodes. The whole purpose of invoke() operation is to send the entry
processor to server nodes instead of transferring the data across network.
The mapping always exists. Even if there is no actual value in c
On Tue, Mar 14, 2017 at 12:46 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> >
> > Which user operation would result in exception? To my knowledge, user may
> > already be holding the lock and not invoking any Ignite APIs, no?
> >
>
> Yes, this is exactly my point.
>
> Imagine that a
GitHub user ezhuravl opened a pull request:
https://github.com/apache/ignite/pull/1617
ignite-4141 JDBC driver should always set withKeepBinary flag for cache
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Hello everybody!
Denis, I prepared a pull-request and test executed successfully on TeamCity
with awaiting time 500 milliseconds.
Review it please - https://github.com/apache/ignite/pull/1615
Vadim Opolski
2017-03-10 23:04 GMT+03:00 Denis Magda :
> Vadim,
>
> Please prepare a pull-request and
Pavel Tupitsyn created IGNITE-4817:
--
Summary: .NET: Contains fails in LINQ when subquery comes from a
variable
Key: IGNITE-4817
URL: https://issues.apache.org/jira/browse/IGNITE-4817
Project: Ignite
Hi all! When we invoke EntryProcessor with a given key would it be executed
on a separate node, where the key resides? What if there is no key mapping.
--
*Best Regards,*
*Kuznetsov Aleksey*
IgniteTransactionState implememntation contains IgniteTxEntry's which is
supposed to be transferable
пн, 13 мар. 2017 г. в 19:32, Dmitriy Setrakyan :
> It sounds a little scary to me that we are passing transaction objects
> around. Such object may contain all sorts of Ignite context. If some dat
>
> Which user operation would result in exception? To my knowledge, user may
> already be holding the lock and not invoking any Ignite APIs, no?
>
Yes, this is exactly my point.
Imagine that a node already holds a lock and another node is waiting for
the lock. If all partition nodes leave the gr
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/1616
IGNITE-4806 Fix infinite classloading discovery
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite IGNITE-4806
Alternatively
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/1608
---
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 enab
36 matches
Mail list logo
