Igniters,
I remember that we have added automatic node failure in case of unknown
errors or events that may be fatal. Does this extend to the actual user
exceptions?
The reason I am asking is because of this thread on SO:
same effect: email
> will be sent)
> -- dev. list and CC to contributor's email
>
> - and keep ticket unassigned
> -- until contributor starts
> -- or going to start actual implementation.
>
> Sincerely,
> Dmitriy Pavlov
>
> сб, 28 июл. 2018 г. в 15:50, Dmitriy Setrakya
>
Please do.
>
> Sincerely,
> Dmitriy Pavlov
>
> сб, 28 июл. 2018 г. в 3:28, Dmitriy Setrakyan :
>
> > On Fri, Jul 27, 2018 at 3:02 PM, Dmitriy Pavlov
> > wrote:
> >
> > > Hi Igniters,
> > >
> > > I would discourage all Igniters
> > > > > > >
> > > > > > > > This is a great question. Will the service be able to
> continue
> > > > > > operating
> > > > > > > > after the cache is destroyed? If not, I would undeploy it
> > &
On Fri, Jul 27, 2018 at 3:02 PM, Dmitriy Pavlov
wrote:
> Hi Igniters,
>
> I would discourage all Igniters from direct assigning issues to anyone
> else. Of cource excepting the case it was directly discussed with asignee.
> Any contributor should be able to assign issue to himself.
>
> I left
at on user-list, not here, to vote for
> > the deprecation like this.
> >
> > 2018-07-26 11:23 GMT+03:00 Vladimir Ozerov :
> >
> > > I meant LOCAL + non-LOCAL transactions of course.
> > >
> > > On Wed, Jul 25, 2018 at 10:42 PM Dmitriy Setrakyan &
Dmitriy,
I would stop using the word "hashcode" in this context. Hash code has a
special meaning in Ignite and is used to determine key-to-node affinity. I
agree that passing "cache_name" is the best option. I have no idea when
"cache_name" is not going to be known and do not think we need to
Let's suppose that some transaction is trying to update values A and B:
*tx.start() *
> *cache.put("A", 1);cache.put("B", 2); *
*tx. commit();*
If you use READ_COMMITTED isolation level, it is possible that you will
read the new value of A and the old value of B. If you need to make sure
I am still confused. Let's work through an example. Suppose I have a cache
named "my_cache" and I want to put an entry with key "a" and value "1".
In Java, this code will look like this:
> *IgniteCache<...> myCache = ignite.cache("my-cache");myCache.put("a", 1);*
How will the same code look
easier and faster than fixing all bugs.
> >
> > 2018-07-25 11:51 GMT+03:00 Dmitriy Setrakyan :
> >
> > > I would stay away from deprecating such huge pieces as a whole LOCAL
> > cache.
> > > In retrospect, we should probably not even have LOCAL ca
.org/jira/browse/IGNITE-3392
> On Tue, Jul 24, 2018 at 3:01 PM Vyacheslav Daradur
> wrote:
> >
> > Got it.
> >
> > Yes, we will preserve this behavior.
> >
> > Thanks!
> > On Tue, Jul 24, 2018 at 2:20 PM Dmitriy Setrakyan
> wrote:
> > >
e
> fly, unlike Ignite cache,
>
> - there could be other architectural choices too.
>
> I will be glad to answer your further questions. If you have suggestions
> about higher-level abstractions and their use cases, please let me know.
>
> Dmitry
>
> On 07/24/2018 10
I would stay away from deprecating such huge pieces as a whole LOCAL cache.
In retrospect, we should probably not even have LOCAL caches, but now I am
certain that it is used by many users.
I would do one of the following, whichever one is easier:
- Fix the issues found with LOCAL caches,
Yes, looks strange? Why is the hash code part of API?
On Tue, Jul 24, 2018, 13:38 Igor Sapego wrote:
> Ok, I've quickly looked through API and I have a questions. Here
> is the code from the example:
>
> cache_name = 'my cache'
> hash_code = hashcode(cache_name)
> cache_create(conn, cache_name)
t services. There are
> > > > some tests that expect such behavior.
> > > >
> > > > Services assignments are managed by a predicate only
> > > > (ServiceConfiguration#setNodeFilter(IgnitePredicate).
> > > >
> > > > Should deployment o
On Sat, Jul 21, 2018 at 5:22 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Actually, I would go even further: only allocate a data region on a node
> when the first cache assigned to this region is deployed on that node.
> Because issue is broader than client nodes and local
Val, thanks for pointing this out.
I would actually not allocate any off-heap memory on the client side unless
we see Local caches in the configuration. This is such a rare case, that we
can ignore it altogether.
D.
On Fri, Jul 20, 2018 at 3:59 PM, Valentin Kulichenko <
Users rarely run examples
> on multiple machines.
>
> чт, 19 июля 2018 г. в 5:30, Dmitriy Setrakyan :
>
> > I am confused, the TcpDiscoveryVmIpFinder will only discover nodes with
> > specified list of IPs. Don't we have examples that require remote nodes
> to
> >
Why can't we use a combination of both, VM and Multicast IP finders?
D.
On Thu, Jul 19, 2018 at 8:28 AM, Stanislav Lukyanov
wrote:
> Yakov,
>
> First, it doesn’t seem likely that many people would run examples on
> several machines. Even if someone would, they’d probably start doing so
> after
I am confused, the TcpDiscoveryVmIpFinder will only discover nodes with
specified list of IPs. Don't we have examples that require remote nodes to
join?
D.
On Wed, Jul 18, 2018 at 7:52 AM, Stanislav Lukyanov
wrote:
> > It can seem not important, but saves a minute for everyone.
> No, it
Dmitriy,
I think you should file an INFRA ticket and ask if this is possible.
D.
On Wed, Jul 18, 2018 at 3:12 PM, Denis Magda wrote:
> Dmitriy,
>
> Things for clearing the things out. No objections from my side then.
>
> Let's see what other Ignite fellows think on your proposal. Someone
; Before uploading, please check this [1] build.
> > > > > >>>>>>
> > > > > >>>>>>
> > > > > >>>>>> [1]
> > > > > >>>>>>
> > > > > >>>
On Mon, Jul 16, 2018 at 5:42 PM, Yakov Zhdanov wrote:
> Dmitry, let's have only getNext() same as jdbc. All other shortcuts seem to
> overload API without adding much value.
>
Agree. Do you mind creating a ticket?
Is there a reason why 2.6 has not been uploaded to the website yet?
D.
On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura wrote:
> Igniters,
>
> Apache Ignite 2.6.0 release (RC1) has been accepted.
>
> 5 "+1" binding votes received:
>
> - Alexey Goncharuk
> - Alexey Kuznetsov
> - Andrey Gura
> -
Well, instead of getFirst(), I would have getNext(). This way we do not
have to keep the first entry forever, which could present a problem in case
if entry is too large.
As far as initializing keepAll() to false - completely agree.
D.
On Mon, Jul 16, 2018 at 4:43 PM, Alexey Goncharuk <
This question has been asked of the Stack Overflow:
https://stackoverflow.com/questions/51314852/is-there-a-workaround-to-use-thin-client-with-cache-expiry-policy-in-apache-igni
Would be nice to provide an answer. Pavel, can you respond?
Thanks,
D.
On Thu, Jul 12, 2018 at 3:22 PM, Yakov Zhdanov wrote:
> If events are working when grid is not active and adding/removing listeners
> is also possible then I agree/
>
The events should be working. The cluster is not active, but the node is
started and should be able to fire events.
AG, can you
On Thu, Jul 12, 2018 at 3:08 PM, Yakov Zhdanov wrote:
> Its counter event on_after_deactivated cannot be fired through event
> notification support. Therefore, it is better to gather such events in
> LifeCycleEventType.
>
Why not? After deactivation the node should still be usable and should be
On Mon, Jul 9, 2018 at 1:32 PM, Yakov Zhdanov wrote:
> > What is the difference between a lifecycle even and regular events?
>
> Lifecycle events should be used when there is no opportunity for Ignite to
> fire regular event, e.g. node stops or is not started yet. Please see
>
BTW, I have added a ticket for the configuration template [1] and linked it
to the ticket originally created by Yakov [2].
[1] https://issues.apache.org/jira/browse/IGNITE-8986
[2] https://issues.apache.org/jira/browse/IGNITE-8951
D.
On Wed, Jul 11, 2018 at 6:58 PM, Yakov Zhdanov wrote:
>
Dmitriy Setrakyan created IGNITE-8986:
-
Summary: Need to add configuration validation template on startup
Key: IGNITE-8986
URL: https://issues.apache.org/jira/browse/IGNITE-8986
Project: Ignite
p stop.
> > REST:
> > * Fixed serialization of BinaryObjects to JSON.
> >
>
>
> Apache Ignite In-Memory Data Fabric 2.5
>
> ---
>
>
> 2018-07-11 9:54 GMT+03:00 Dmitriy Setrakyan :
>
> > Andrey, this is the link
uld check it using provided links.
>
>
>
> ср, 11 июл. 2018 г., 5:41 Andrey Gura :
>
> > Dmitry,
> >
> > It is emergency release so we have very short list of changes. You could
> > check it using provided links.
> >
> >
> > ср, 11 июл. 2018 г., 3:01
any sync warranty.
>
>
> [1]
> org.apache.ignite.internal.processors.cache.distributed.
> near.GridNearTxLocal#rollbackOnlyProxy
> [2] https://github.com/apache/ignite/pull/4036
>
> пн, 9 июл. 2018 г. в 7:04, Dmitriy Setrakyan :
>
> > Anton, how do you plan to rollbac
Not sure if this is worth a down vote, but the release notes seem like a
copy of 2.5 release. I think 2.6 should have its own release notes.
D.
On Tue, Jul 10, 2018 at 8:02 PM, Andrey Gura wrote:
> Igniters,
>
> We've uploaded a 2.6.0 release candidate to
>
What about an idea to have a validation template file (e.g.
ignite-validate.xml), and make sure on startup that all config properties
specified in that file match. This way a user could put this file somewhere
on a shared network drive and have an extra degree of confidence that the
configuration
Dmitriy Setrakyan created IGNITE-8977:
-
Summary: Need to update distributed SQL page
Key: IGNITE-8977
URL: https://issues.apache.org/jira/browse/IGNITE-8977
Project: Ignite
Issue Type
Dmitriy Setrakyan created IGNITE-8976:
-
Summary: Add native persistence section to Key-Value data grid page
Key: IGNITE-8976
URL: https://issues.apache.org/jira/browse/IGNITE-8976
Project: Ignite
motely.
>
> Yakov,
> could you please review the code?
>
> [1] https://github.com/apache/ignite/pull/4036 (TC checked)
> [2]
> org.apache.ignite.internal.processors.cache.distributed.
> near.GridNearTxLocal#rollbackOnlyProxy
>
> пт, 1 июн. 2018 г. в 23:33, Dmit
rget to provide that other
> separate file with printed configuation. Log file is our best shot since
> it's what usually gets reported.
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-07-07 0:23 GMT+03:00 Dmitriy Setrakyan :
>
> > Can we print out the configuration to
t;
> Evgenii
>
> 2018-07-06 1:10 GMT+03:00 Dmitriy Setrakyan :
>
> > On Thu, Jul 5, 2018 at 1:55 AM, Evgenii Zhuravlev <
> > e.zhuravlev...@gmail.com>
> > wrote:
> >
> > > Guys,
> > >
> > > Do we really need events for activation
Can we print out the configuration to a separate file? Moreover, I think we
should also print out the configuration differences between nodes, whenever
new nodes join topology.
D.
On Fri, Jul 6, 2018 at 6:51 AM, Ilya Kasnacheev
wrote:
> Hello!
>
> I was working on
On Thu, Jul 5, 2018 at 1:55 AM, Evgenii Zhuravlev
wrote:
> Guys,
>
> Do we really need events for activation/deactivation? We already have a
> ticket for implementation lifecycle events for it:
> https://issues.apache.org/jira/browse/IGNITE-5427, won't it be enough?
>
Hm... I think these two
gt; cache operations*." and "*If topology validator is not configured, then the
> cluster topology is always considered to be valid.*"
>
Yup. In this case, my answer is correct.
>
> Thanks,
>
> On Mon, Jul 2, 2018 at 4:21 PM, Dmitriy Setrakyan
> wrote:
>
> > On
Do we really not have events in Ignite for cluster activation?
Alexey Goncharuk, can you please comment?
D.
On Mon, Jul 2, 2018 at 1:34 AM, kcheng.mvp wrote:
> Dear igniters,I am going to pick up
> https://issues.apache.org/jira/browse/IGNITE-8376, and did some research
> based on the
On Mon, Jul 2, 2018 at 4:03 PM, John Wilson wrote:
> Hi,
>
>
>1. What exactly is a cluster topology? What makes a cluster topology
>invalid for further cache operations?
>
Cluster topology is a set of Ignite nodes in the cluster. I do not think a
cluster topology could be invalid on its
p
> > independently of other non-core features.
> > For me Ignite way is providing to our users a fast and convenient way to
> > solve their problems with good performance and durability. We have the
> > problem with storing large data, we should solve it.
> > About o
Ken, can you please repost this question to the user list (not dev list).
This is more of a user list question, so you should get a faster response
there.
D.
On Fri, Jun 29, 2018 at 7:18 PM, kcheng.mvp wrote:
> Thank you very much! I can see my post now.
>
> by the way, can you take a look
level information about how it should look.
>
> сб, 30 июн. 2018 г. в 19:40, Dmitriy Setrakyan :
>
> > Pavel, it definitely makes sense. Do you have a design in mind?
> >
> > D.
> >
> > On Sat, Jun 30, 2018, 07:24 Pavel Kovalenko wrote:
> >
> > &
Pavel, it definitely makes sense. Do you have a design in mind?
D.
On Sat, Jun 30, 2018, 07:24 Pavel Kovalenko wrote:
> Igniters,
>
> I would like to start a discussion about designing a new feature because I
> think it's time to start making steps towards it.
> I noticed, that some of our
Ken, seems like you have subscribed. Generally, all you have to do is send
an email to dev-subsci...@ignite.apache.org and then simply reply to the
confirmation email.
D.
On Fri, Jun 29, 2018 at 5:01 AM, Ken Cheng wrote:
> Thanks,
> Ken Cheng
>
Is there an IEP for it where the community can read about the feature set
that will be supported by the Python client?
D.
On Thu, Jun 28, 2018 at 11:39 AM, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com> wrote:
> Hello Ignite developers!
>
> I would like to bring to your attention, that the
On Tue, Jun 26, 2018 at 9:58 AM, Evaldas Miliauskas <
e.miliaus...@stacktome.com> wrote:
> I see, could you give an example about "changing arg name manually"? Or do
> you mean only constant values can be passed as args in that case?
>
What I meant is passing an actual value instead of the "?".
On Tue, Jun 26, 2018 at 9:23 AM, Evaldas Miliauskas <
e.miliaus...@stacktome.com> wrote:
> Hey, I was trying to test queries that use condition "? is null" to be
> able to use explain command and see what query plan is generated.
>
Got it. Currently web console accepts SQL statements, not JDBC
Hi Evaldas,
I am not sure why do you need to pass the "?" from the Web Console? Why not
just pass the real parameter?
D.
On Mon, Jun 25, 2018 at 7:05 PM, Evaldas Miliauskas <
e.miliaus...@stacktome.com> wrote:
> Right now I cannot execute a following query in Web Console:
> "select count(*)
On Fri, Jun 22, 2018 at 6:13 AM, Sergey Chugunov
wrote:
> Dmitriy,
>
> Answering to your questions:
>
> 1) policy applies only to servers as coordinator never waits for clients in
> PME protocol;
>
Sergey, to my knowledge, clients do participate in PME (although would be
interesting to find out
Hi Sergey,
This is probably the most important IEP we have. I am assuming that after
this gets fixed, Ignite cluster will never come to a freezing state.
I propose to name the enum *PmeStopPolicy*. Here are my suggestions:
- NONE - will result in logging the state
-
t;
>
> On Tue, Jun 19, 2018 at 10:06 PM Dmitriy Setrakyan
> wrote:
> >
> > Hi Vyacheslav,
> >
> > How about service redeployment in case if user wants to update the code?
> Is
> > this planned?
> >
> > D.
> >
>
Denis,
I think we should list this integration somewhere on the Ignite website. On
top of that, the integration uses Ignite Go client, which also deserves a
mention.
D.
On Mon, Jun 18, 2018 at 9:35 AM, Denis Magda wrote:
> Kenneth, thanks for supporting Ignite at usql level! Excellent news!
On Mon, Jun 18, 2018 at 9:45 AM, Denis Magda wrote:
> Guys,
>
> Have a look at Hazelcast. They provide both approaches - installation with
> a package management system + binary (or zip archives downloads):
> https://hazelcast.org/clients-languages/
>
> It will be great to provide Ignite
rly install it:
>
> Node.js: $ npm install <...>
> or
> Python: $ pip install <...>
>
> So the proposal is not really applicable to these clients.
>
> Pavel
>
>
>
> On Sat, Jun 16, 2018 at 12:45 AM, Dmitriy Setrakyan >
> wrote:
&
+1
On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda wrote:
> Igniters,
>
> Presently, all our thin clients and SQL drivers are stored in the main
> Ignite repository. That's totally fine, I wouldn't change anything in here.
>
> But, what I would encourage us to contemplate on is how a user gets
Dmitriy, great job! Very important fix to a very bad problem in the product
that could cause data consistency issue.
Will it be included into 2.6, or will we have to wait for 2.7?
D.
On Thu, Jun 14, 2018 at 6:53 AM, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:
> Folks,
>
> I fixed
In continuation to my previous email about INFO level log output, we also
have a big problem with QUIET log mode. Here is an example of a single node
output after another node joined and left 3 times:
[22:50:23] Ignite node started OK (id=931fcf60)
> [22:50:23] Topology snapshot [ver=4,
Dmitriy Setrakyan created IGNITE-8803:
-
Summary: Need to fix Ignite QUIET log output
Key: IGNITE-8803
URL: https://issues.apache.org/jira/browse/IGNITE-8803
Project: Ignite
Issue Type
Dmitriy Setrakyan created IGNITE-8802:
-
Summary: Need to fix Ignite INFO output
Key: IGNITE-8802
URL: https://issues.apache.org/jira/browse/IGNITE-8802
Project: Ignite
Issue Type
On Wed, Jun 6, 2018 at 10:40 PM, Peter Ivanov wrote:
> Dmitriy,
>
>
> What kind of instructions? Systemd or stand-alone?
> I thought we have already agreed that systemd services are not eligible for
> Windows 10 WSL.
>
> So have I to check that Debian, Ubuntu and SUSE environments for Windows 10
rying to move the conversation in this direction.
> > > >
> > > > Is it possible to install and run Cassandra using DEB from that
> > emulation
> > > > environment on Windows? If yes, then we should spend our efforts
> > ad
Vladimir,
Can you please explain how our users will be affected? What does it mean to
use "spatial" indexes in Ignite?
D.
On Wed, Jun 6, 2018 at 12:54 AM, Vladimir Ozerov
wrote:
> Igniters,
>
> New H2 version 1.4.197 [1] was released recently. It contain a lot of
> changes (>1000 commits) and
On Tue, Jun 5, 2018 at 12:12 PM, Petr Ivanov wrote:
> Dmitriy,
>
>
> I will check soon and see what can be done to overcome this.
>
Thanks! Looking forward to your feedback.
>
> Yet, I still doubt that running Apache Ignite packed in DEB under Windows
> 10 WSL Ubuntu is a plausible user case.
On Tue, Jun 5, 2018 at 1:54 PM, Sergey Kozlov wrote:
> Hi
>
> For Windows users we should provide Windows installer (.exe or .msi) that
> set up and install AI as service. But that task requires significant
> efforts and makes sense to start in that way after stabilization DEB/RPM
>
gniters.
> >> > > > > > >
> >> > > > > > > Actually, I don't understand why we should merge in master
> >> something
> >> > > > > > > broken.
> >> > > > > > > Currently, Ignite is not rea
eptible to outside impact.
> And to be able to run Apache Ignite as a standalone process — it is enough
> to login as ignite user (as it is mentioned in documentation) and run
> ignite.sh as usual.
>
>
>
>
> > On 5 Jun 2018, at 08:00, Dmitriy Setrakyan
> wrote:
> &g
Petr,
I think it was Denis who reworked the documentation. In any case, if you
see something lacking you can fix it.
Just to clarify, are you suggesting that you don't have to be root to run
the Ignite process after the package install?
D.
On Mon, Jun 4, 2018 at 9:31 PM, Petr Ivanov wrote:
>
gt; >> wrote:
> >> > Igniters,
> >> > I think I can do it. As I see we already have JCache TCK tests in TC.
> >> > Can I take somewhere settings/script which we are using?
> >> >
> >> > 2018-05-23 2:58 GMT+03:00 Dmitriy Setrakyan :
&g
Here is my list:
1. Remove the requirement to run Ignite scripts as root. This will be a
huge No in most environment and we should fix it.
2. Add Ignite "bin" folder to PATH, so all Ignite scripts will be
executable without specifying the whole path name (not sure if it is
already
pped via symlink
> to /var/lib/apache-ignite/log because /var/lib/apache-ignite/ (main work
> dir which in its turn is mapped via symlink to
> /usr/share/apache—ignite/work) is the place where running node of Apache
> Ignite will write it’s logs.
>
>
>
> > On 4 Jun 2018,
ttps://issues.apache.org/jira/browse/IGNITE-8671?focusedCom
> mentId=16500123=com.atlassian.jira.plugin.system.
> issuetabpanels:comment-tabpanel#comment-16500123
>
>
>
>
> > On 3 Jun 2018, at 10:24, Dmitriy Setrakyan
> wrote:
> >
> > Peter,
> >
> &g
()" will throw the
> exception.
>
> On Sat, Jun 2, 2018 at 4:27 PM, Dmitriy Setrakyan
> wrote:
>
> > Dmitriy, what happens in case of unknown exceptions?
> >
> >
> > On Thu, May 31, 2018 at 6:35 AM, Dmitriy Govorukhin <
> > dmitriy.govoruk...@gmail.co
pplication (see [1]).
> Hope it will be enough.
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8671?
> focusedCommentId=16499157=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-16499157
>
>
>
>
> > On 2 Jun 2018, at 21:57, Dmitri
Apache Ignite
>> installation and how to correctly start Apache Ignite in terms of
>> permissions.
>>
>> File the documentation updates ticket?
>>
>>
>> On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan
>> wrote:
>>
>> > Petr,
>> >
>
; Comments are welcome.
>
> On Thu, May 31, 2018 at 12:53 AM, Dmitriy Setrakyan >
> wrote:
>
> > On Wed, May 30, 2018 at 8:04 AM, Dmitriy Govorukhin <
> > dmitriy.govoruk...@gmail.com> wrote:
> >
> > > Dmitriy,
> > >
> > > I
nite
> manually through ignite.sh with a reference to corresponding documentation
> section, information where to look for the root of Apache Ignite
> installation and how to correctly start Apache Ignite in terms of
> permissions.
>
> File the documentation updates ticket?
>
>
> can do it as a separate task)
> - rollback can be implemented on all Grid*TxLocal or even at Grid*TxRemote
> :)
>
It is completely wrong design to have any kind of transaction commit or
rollback action from inside of any event.
>
> [1] https://issues.apache.org/jira/browse/IGNIT
ion.
>
> BTW, rollback also available only at events produced by GridNearTxLocal.
>
> пт, 1 июн. 2018 г. в 16:29, Dmitriy Setrakyan :
>
> > Ok, sounds good.
> >
> > I till have more comments:
> >
> >1. I think you have missed EVT_TX_PREPARED event
> >2.
EVT_CACHE_OBJECT_PUT,
> EVT_CACHE_OBJECT_READ,
> EVT_CACHE_OBJECT_REMOVED,
> EVT_CACHE_OBJECT_LOCKED,
> EVT_CACHE_OBJECT_UNLOCKED,
> EVT_CACHE_OBJECT_EXPIRED
> };
>
>
> чт, 31 мая 2018 г. в 20:48, Dmitriy Setrakyan :
>
>
ing Apache Ignite
> as standalone process – executing /usr/share/apache-ignite/bin/ignite.sh
> with parameters will start Apache Ignite node as if it was delivered by
> binary archive.
>
>
>
> On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan
> wrote:
>
> > Petr
ncurrency()
> - implicit()
> - isInvalidate()
> - state()
> - timeout()
>
> now available at any tx state change event.
>
>
> As usual, full code listing available at
> https://github.com/apache/ignite/pull/4036/files
>
>
> вт, 29 мая 2018 г. в 20:41, Dmitriy
2, Petr Ivanov wrote:
> >
> > Filed https://issues.apache.org/jira/browse/IGNITE-8671 <
> https://issues.apache.org/jira/browse/IGNITE-8671>
> >
> >
> >
> >> On 31 May 2018, at 17:56, Dmitriy Setrakyan <mailto:dsetrak...@apache.org>> wrote
On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov wrote:
> I’ll start the investigation.
>
Can you please file a ticket so we can track it?
gt; Can you try starting dbus manually? sudo service dbus start
>
> If it still does not work, I will have to held an investigation on running
> systemd services on Windows 10 WSL
>
>
> On Thu, 31 May 2018 at 00:31, Dmitriy Setrakyan
> wrote:
>
> > On Wed, May 30, 2018 at 2:
On Wed, May 30, 2018 at 2:06 AM, Paul Anderson wrote:
> cool and again congrats also I'm developing a cute little thing
> for 2.6 will show you when it's done
>
We love surprises :)
On Wed, May 30, 2018 at 7:36 AM, Igor Sapego wrote:
> Most probably, when I'm done with the C++ thin client.
>
Sounds good. Do you have some estimate for when that might be?
On Wed, May 30, 2018 at 8:04 AM, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:
> Dmitriy,
>
> I agree that in normal mode we should stop and report that error according.
> I prefer to add ability skip records for offline mode.
>
Sounds good.
On Wed, May 30, 2018 at 2:09 PM, Peter Ivanov wrote:
> Dmitriy,
>
> What kind of Ubuntu installation do you have (and what version)?
> Is it WSL under Windows 10 or containerized (docker)?
>
>
Windows Ubuntu App -
https://docs.microsoft.com/en-us/windows/wsl/install-win10
D.
ion will be more compact and precise.
>
> There is no such option for YUM (as far as I am aware of).
>
>
>
> > On 30 May 2018, at 17:16, Dmitriy Setrakyan
> wrote:
> >
> > Petr,
> >
> > Can you tell me what this flag does: "--no-install-recommend
Dmitriy,
I think the behavior for offline and online iterator is fundamentally
different. I do not think it is OK to skip records during normal operation.
In my view, we should report an error and stop. However, when offline, it
is OK to report an error and continue in my view.
D.
On Wed, May
n-options <https://apacheignite.readme.
> io/docs/getting-started#alternative-installation-options>
> Snippet "DEB repository setup"
>
>
>
>
> > On 30 May 2018, at 16:59, Dmitriy Setrakyan
> wrote:
> >
> > Petr, can you provide a link to the Debi
On Wed, May 30, 2018 at 5:40 AM, Igor Sapego wrote:
> By the way, ODBC does not currently support streaming.
>
Igor, and when do you plan to add this support?
; https://ignite.apache.org/download.cgi#rpm-package>
> >> [2] https://apacheignite.readme.io/docs/getting-started#
> section-rpm-deb-packages-installation <https://apacheignite.readme.
> io/docs/getting-started#section-rpm-deb-packages-installation>
> >>
> &
101 - 200 of 1824 matches
Mail list logo
