Anton,
Switching a partition to and from the SHRINKING state will require
intricate synchronizations in order to properly determine the start
position for historical rebalance without PME.
I would still go with an offline-node approach, but instead of cleaning the
persistence, we can do effective
Alexey,
Sounds good to me.
On Thu, Oct 3, 2019 at 10:51 AM Alexey Goncharuk
wrote:
> Anton,
>
> Switching a partition to and from the SHRINKING state will require
> intricate synchronizations in order to properly determine the start
> position for historical rebalance without PME.
>
> I would s
Anton, do you think we should file a single ticket for this or should we go
with an IEP? As of now, the change does not look big enough for an IEP for
me.
чт, 3 окт. 2019 г. в 11:18, Anton Vinogradov :
> Alexey,
>
> Sounds good to me.
>
> On Thu, Oct 3, 2019 at 10:51 AM Alexey Goncharuk <
> alexe
Yes, my expectation was "~" to be the user home as well, too bad we missed
this during the review. The current process directory is broken because a
simple "cd" will make the persistent data disappear, which may be even
worse than the temp directory.
чт, 3 окт. 2019 г. в 01:45, Denis Magda :
> I
Alexey,
As for me, it does not matter will it be IEP, umbrella or a single issue.
The most important thing is Assignee :)
On Thu, Oct 3, 2019 at 11:59 AM Alexey Goncharuk
wrote:
> Anton, do you think we should file a single ticket for this or should we go
> with an IEP? As of now, the change doe
As for .NET. Should not we define IGNITE_HOME for it?
чт, 3 окт. 2019 г. в 12:13, Ivan Pavlukhin :
>
> Folks,
>
> I am with Ilya here. I remind that we are talking not about general
> case for Ignite usage. Generally IGNITE_HOME should be defined.
> Otherwise we fallback to a default, and user.dir
Folks,
I am with Ilya here. I remind that we are talking not about general
case for Ignite usage. Generally IGNITE_HOME should be defined.
Otherwise we fallback to a default, and user.dir usually points to a
directory where java launcher command was called (work dir).
user.home seems to cause mor
Pavel Kovalenko created IGNITE-12255:
Summary: Cache affinity fetching and calculation on client nodes
may be broken in some cases
Key: IGNITE-12255
URL: https://issues.apache.org/jira/browse/IGNITE-12255
Ivan, which vendors place files into current work dir, can you please give
an example?
> Generally IGNITE_HOME should be defined
This is an inconvenience for the users, bad usability.
As a user, why would I want to define a system-wide property just to use
some library?
> As for .NET. Should not
Pavel.
> As a user, why would I want to define a system-wide property just to use
> some library?
Why do you think Ignite is a library?
May be the root of usability issues in using same distribution for a library
and server side dbms?
В Чт, 03/10/2019 в 13:40 +0300, Pavel Tupitsyn пишет:
> Iv
Nikolay,
Ignite is widely used in embedded scenarios; the ability to process data
in-process locally is very powerful and I see no reason why we should
remove it. I absolutely agree with Pavel T. on the subject. As an example,
both SQLite, and rocksdb are distributed as a library, so I see no issu
Alexey.
> Ignite is widely used in embedded scenarios; the ability to process data
> in-process locally is very powerful and I see no reason why we should
> remove it
I don't propose to remove something.
I wrote about "same distribution".
Seems, we should have different defaults and even distrib
Ilya Kasnacheev created IGNITE-12256:
Summary: Fix double invocation of javaMajorVersion in scripts
Key: IGNITE-12256
URL: https://issues.apache.org/jira/browse/IGNITE-12256
Project: Ignite
Alexey Zinoviev created IGNITE-12257:
Summary: [ML] Add Feature Filter for ML Partitioned Dataset
Key: IGNITE-12257
URL: https://issues.apache.org/jira/browse/IGNITE-12257
Project: Ignite
Hello!
I have found that this call is not needed at all, so I've started
https://issues.apache.org/jira/browse/IGNITE-12256
Regards,
--
Ilya Kasnacheev
вт, 24 сент. 2019 г. в 06:44, liyuj <18624049...@163.com>:
> Hi,
>
> I have pushed PR: 6899, and I hope the community will merge as soon as
>
Hello!
I think that you should not attempt to fix Cache Store if you don't have
first-hand experience of using it. Please redirect your efforts to some
area where, as the bare minimum, you are able to write such examples
yourself.
Regards,
--
Ilya Kasnacheev
ср, 11 сент. 2019 г. в 19:13, Amit
Pavel,
> Ivan, which vendors place files into current work dir, can you please give an
> example?
Cockroachdb stores files relative to current work dir (yes, "cd"
sensitive). As I understood aforementioned SQLite do the same [1].
> In this case users won't even be able to use Maven or NuGet, le
Ivan,
Regarding you question about Lucene search response.
*IndexSearcher.search()* always returns result sorted at least by *score
*(*relevance*) or by defined *Sort *which includes ordering fields and
rules.
This means than even for now *GridLunceneIndex* result will be incorrect in
case of
Denis,
Thank you for your attention to this.
as for now, the https://issues.apache.org/jira/browse/IGNITE-12189 ticket
is still pending review.
Do we have a chance to move it forward somehow?
BR,
Yuriy Shuliha
пн, 30 вер. 2019 о 23:35 Denis Magda пише:
> Yuriy,
>
> I've seen you opening a pull
Hello, Ivan.
Thanks for feedback.
Initial IEP [1] naming was changed during code review.
I updated the IEP [1] with the current naming.
Can you take a look and check is all clear now?
[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392
В Ср, 02/10/2019 в 17:21 +0300,
Ilya,
> I think that you should not attempt to fix Cache Store if you don't have
> first-hand experience of using it.
Not sure that I understand "first-hand experience" properly. But it
seems to me that almost every Ignite developer started contribution
without first-hand experience in one or ano
>
> Seems, we should have different defaults and even distributions for
> different usage scenarios.
>
I still do not understand why defaults should be different for embedded and
"traditional RDBMS-like" installations. Having different defaults will
likely confuse users, not make usability easier.
Yuri,
I've done with review.
No crime found, but trivial compatibility bug.
On Thu, Oct 3, 2019 at 3:54 PM Yuriy Shuliga wrote:
> Denis,
>
> Thank you for your attention to this.
> as for now, the https://issues.apache.org/jira/browse/IGNITE-12189 ticket
> is still pending review.
> Do we have
Hello!
I want to point out that I didn't change this location (current dir). It
was already implemented when I raised this issue, the only change I did was
to swap current dir/work to current dir/ignite/work to avoid confusion
whose work dir that is.
I also communicated this to you all in ML when
> Cannot tell about NuGet. Maven is typically used during development,
usually there is no Maven in production deployments.
NuGet and Maven are very similar. Yes, both of them are build-time tools,
production is unrelated.
For production-ready deployments we can expect users to tweak Ignite to
the
Hi
I'm not sure that node offline is a best way to do that.
Cons:
- different caches may have different defragmentation but we force to stop
whole node
- offline node is a maintenance operation will require to add +1 backup to
reduce the risk of data loss
- baseline auto adjustment?
- impact t
Hello!
We can try and fallback to home dir with warning, when file cannot be
created in current dir.
WDYT?
Regards,
--
Ilya Kasnacheev
чт, 3 окт. 2019 г. в 20:05, Pavel Tupitsyn :
> > Cannot tell about NuGet. Maven is typically used during development,
> usually there is no Maven in product
Hi, thanks for starting this thread!
SQL folks, could you please confirm that's neither known nor expected
limitation? If that's a real issue then we will just need to go through a
standard contribution process.
-
Denis
On Thu, Oct 3, 2019 at 12:19 PM Hemambara wrote:
> We have to add indexes
Ilya, fallback is a good idea.
Still I'd prefer to have user.home as a default, and fallback to user.dir
when home does not work for some reason.
On Thu, Oct 3, 2019 at 11:07 PM Ilya Kasnacheev
wrote:
> Hello!
>
> We can try and fallback to home dir with warning, when file cannot be
> created in
Igniters,
There is good news. GridGain made its distribution of Web Console
completely free. It goes with advanced monitoring and management dashboard
and other handy screens. More details are here:
https://www.gridgain.com/resources/blog/gridgain-road-simplicity-new-docs-and-free-tools-apache-ign
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
Ok, will try to fix it today
пт, 4 окт. 2019 г., 4:54 :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
> If your changes can lead to this failure(s): We're grateful that you were
> a volunteer to make the contribution to this p
32 matches
Mail list logo
