Ivan Bessonov created IGNITE-12108:
--
Summary: [IEP-35] Migrate Communication Metrics.
Key: IGNITE-12108
URL: https://issues.apache.org/jira/browse/IGNITE-12108
Project: Ignite
Issue Type:
And what about /opt/ignite ?
copy-paste:
"
The basic difference is that /usr/local is for software not managed by the
system packager, but still following the standard unix deployment rules.
That's why you have /usr/local/bin , /usr/local/sbin /usr/local/include
etc...
/opt on the
Dmitriy Govorukhin created IGNITE-12110:
---
Summary: Bugs & tests fixes
Key: IGNITE-12110
URL: https://issues.apache.org/jira/browse/IGNITE-12110
Project: Ignite
Issue Type: Bug
Or instead of a WARNING, we can add a suggestion with a recommendation
for the production environment.
вт, 27 авг. 2019 г. в 11:41, Petr Ivanov :
>
> /opt is either does not exist on fresh system, or has the same restriction:
> no user access without admin intervention.
> /usr/local, /var/lib,
Hi!
The Nabble forum formats emails in a way that makes quoted messages unreadable.
For example, take a look at the latest messages in the following thread:
http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-6-Time-Scope-and-Release-manager-td42944.html
The beginning of
Hello!
I don't see why it should break backward compatibility and protocol. Can
you please elaborate? I imagine that Thin client with TX muxing support
will just send different requests to which server will respond differently.
Why would anything break?
Regards,
--
Ilya Kasnacheev
пн, 26 авг.
Hi Igniters,
Thanks to everyone, https://issues.apache.org/jira/browse/INFRA-18944 created.
For relatively small releases like 2.7.5,2.7.6, it is ok to collect RN
manually, but for a major release, I assume we need a separate field for it.
I also found not completed issue, which could benefit
Ilya,
Sorry, I've just got your first message wrong. I though, you were
proposing to remove ClientConnectorConfiguration altogether, my bad.
Now, about separating ClientConnectorConfiguration and - I do not
propose to make it a copy with the same options. What I was proposing
is to keep common
Hi Igniters,
I agree that user home maybe not the best place from Linux perspective and
philosophy, but "user.home"/ignite/work is more or less portable.
For the Linux environment, we can add a suggestion about where to place
persisted data. For very first testing of Apache Ignite user home
Hello!
I think the nested property approach is correct. Sorry for causing the
confusion.
Regards,
--
Ilya Kasnacheev
вт, 27 авг. 2019 г. в 15:06, Igor Sapego :
> Ilya,
>
> Sorry, I've just got your first message wrong. I though, you were
> proposing to remove ClientConnectorConfiguration
Hi Igniters!
I often meet the following use case.
Id
Company_id
Name
Birthday(dd.mm.)
1 1 John 01.01.2000
2 1 Mike 01.01.2010
3 1 Nick 01.01.2015
Having table Person, it requires to select min and max birth-dates and name
of the youngest and oldest person for each company.
The current
Hi Denis,
AFAIK, nabble forums are service, which resides outside of ASF infra. They
have their separate support/feedback form.
Maybe some PMC members could have some credentials for this service. If so,
please share login info in SVN/private/credentials.
Sincerely,
Dmitriy Pavlov
вт, 27 авг.
/opt is either does not exist on fresh system, or has the same restriction: no
user access without admin intervention.
/usr/local, /var/lib, etc. — all this is implemented in our DEB / RPM packages
already.
For ZIP installation %HOME% seems to be the best approach for "2-click" launch.
Later
Hello!
I think you should go ahead and create a JIRA ticket about it, then someone
(or even you) can check it and fix it.
Regards,
--
Ilya Kasnacheev
пн, 26 авг. 2019 г. в 09:17, Sunny Chan, CLSA :
> Hello,
>
>
>
> In the GridCacheWriteBehindStore
>
change the script to not fail
silently and print at least some hint if it terminates early?
вт, 27 авг. 2019 г. в 18:27, Sergey Antonov :
> Hi everyone!
>
> Issue 3 fixed in master.
> In master control.sh now is:
> *> control.sh --help*
>
> Control utility [ver. 2.8.0-SNAPSHOT#
Hi Ilya, Diana,
I've added permissions, please double-check.
Ilya, I've added your account to Administrators group, so now you could add
contributors in JIRA.
Diana, I found ASF JIRA user Diana Iakovleva (Diana) and added this user to
the contributors' group. Now you should be able to assign an
Alexey Goncharuk created IGNITE-12113:
-
Summary: control.sh terminates silently when JAVA_HOME is not set
Key: IGNITE-12113
URL: https://issues.apache.org/jira/browse/IGNITE-12113
Project: Ignite
9 г. в 18:27, Sergey Antonov :
>
>> Hi everyone!
>>
>> Issue 3 fixed in master.
>> In master control.sh now is:
>> *> control.sh --help*
>>
>> Control utility [ver. 2.8.0-SNAPSHOT#20190827-sha1:DEV]
>> 2019 Copyright(C) Apache Software Foundation
>&g
Hi,
I'd like to contribute to Ignite project, so can you please give to user
Diana necessary rights to be able to work on tickets?
Full name: Diana Iakovleva
Thanks,
Diana
Ilya, Igor,
Nested property is what exactly I've done in the last fix.
ClientConnectorConfiguration now includes ThinClientConfiguration which
contain only one property MaxActiveTxPerConnection for now.
Pavel,
Why do you think that nested ThinClientConfiguration is more confusing than
property
Ok, seems like we came to a consensus. Let’s ensure that the path for our
work dir is user.dir/ignite/work and restart the vote.
Denis
On Tuesday, August 27, 2019, Ilya Kasnacheev
wrote:
> Hello!
>
> I have took the liberty to implement the change to existing code base to
> remove concern
Moti Nisenson-Ken created IGNITE-12114:
--
Summary: Missing information from JavaDoc - CacheConfiguration
setGroupName
Key: IGNITE-12114
URL: https://issues.apache.org/jira/browse/IGNITE-12114
Hello Maxim,
I'll take a look at this soon and make sure the documentation is up to date.
Also, you're always welcome to make suggested edits to the readme.io page.
Thanks!
===
Garrett Alley
Documentation
GridGain Systems
On Tue, Aug 27, 2019 at 10:38 AM Maxim Muzafarov wrote:
> Igniters,
Hi Igniters,
I've updated release process
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process,
now it requires to run [4] Check RC: Licenses, compile, chksum
https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum
as step
Igniters,
I'm worrying about updating the Ignite documentation.
Can you advise who will or should update the Ignite documentation
rebalancing page [2] since the [1] issue has merged to the master
branch and some of the parameters have moved to the
IgniteConfiguration level?
I've marked this
Hi everyone!
Issue 3 fixed in master.
In master control.sh now is:
*> control.sh --help*
Control utility [ver. 2.8.0-SNAPSHOT#20190827-sha1:DEV]
2019 Copyright(C) Apache Software Foundation
User: santonov
Time: 2019-08-27T18:22:45.023
Control utility script is used to execute admin comma
In the current state of the project, we cannot directly compare Ignite
setup process to the one of postgresql or another database. In many Ignite
examples, an embedded node (even with persistence) is started and it is
supposed to run without any additional FS rights grants or init steps. This
may
Denis Chudov created IGNITE-12112:
-
Summary: H2TreeIndex should throw CorruptTreeException with
cacheId, cacheName and indexName
Key: IGNITE-12112
URL: https://issues.apache.org/jira/browse/IGNITE-12112
Hello!
I have took the liberty to implement the change to existing code base to
remove concern about work/ directory:
https://github.com/apache/ignite/pull/6816/files
Some advocacy for this patch:
- Minimal change.
- Storing in user.dir/ignite/work (current directory, e.g. project root)
which
Ivan Bessonov created IGNITE-12109:
--
Summary: The distributed metastorage must support read/write
operation on an inactive cluster.
Key: IGNITE-12109
URL: https://issues.apache.org/jira/browse/IGNITE-12109
Hello, Diana!
Do you have jira username registered on https://issues.apache.org/jira/
You need such an account to be assigned tickets. Please share your username
as soon as you have one.
Regards,
--
Ilya Kasnacheev
вт, 27 авг. 2019 г. в 16:45, Диана Яковлева :
> Hi,
>
> I'd like to
Hi everyone,
Re Issue 3:
That's a good idea, but as far as I remember this was done in
https://jira.apache.org/jira/browse/IGNITE-10279 and is waiting to be
released in Ignite 2.8.
-Artem
On 26.08.2019 15:18, Anton Kalashnikov wrote:
Hello, Igniters.
+1 for Script help usability - issue
Hi Artem, thank you for your reply.
Since this change is on its way, let's wait for 2.8.
Petr Ivanov, Alexey Goncharuck, Ivan Rakov, could you please step in and
provide your feedback related to Issue 1 & 2?
вт, 27 авг. 2019 г. в 17:30, Artem Budnikov :
> Hi everyone,
>
> Re Issue 3:
>
>
Sergey Chugunov created IGNITE-12111:
Summary: Cluster ID and tag: properties to identify the cluster
Key: IGNITE-12111
URL: https://issues.apache.org/jira/browse/IGNITE-12111
Project: Ignite
Dmitriy,
I confirm the first issue but did not get to the bottom of it yet; will
keep you posted.
вт, 27 авг. 2019 г. в 17:34, Dmitriy Pavlov :
> Hi Artem, thank you for your reply.
>
> Since this change is on its way, let's wait for 2.8.
>
>
> Petr Ivanov, Alexey Goncharuck, Ivan Rakov, could
35 matches
Mail list logo
