I agree that ~/work is not expected. I was pretty sure it will be
~/ignite/work or ~/.ignite/work
Sorry, but ~/work I may use for my day job stuff. I don't expect any files
appear there if I start to play with Apache Ignite for the first time.
Since it is a potential usability issue, which is ver
I think it is less confusing than ThinClientConfiguration.
On Fri, Aug 23, 2019 at 8:49 PM Alex Plehanov
wrote:
> Pavel,
>
> ClientConnectorConfiguration is related to JDBC, ODBC and thin clients, the
> new property only related to thin clients. If we put the new property
> directly into Client
I was certainly expecting ~/ignite/work too, not just ~/work
On Mon, Aug 26, 2019 at 10:19 AM Dmitriy Pavlov wrote:
> I agree that ~/work is not expected. I was pretty sure it will be
> ~/ignite/work or ~/.ignite/work
>
> Sorry, but ~/work I may use for my day job stuff. I don't expect any files
Hello, Igniters.
I tried to build Ignite locally from sources on java 12 and got error.
With java8 Ignite builts OK.
Is it expected behavior?
```
dragon:~/download/apache-ignite-2.7.6-src:[]$ mvn clean install
-Pall-java,all-scala,licenses -DskipTests
...
[ERROR] Failed to execute goal
org.ap
Hello, Igniters.
There are plenty of options to store application files in linux:
* /usr/local/ignite
* /var/ignite
* /var/lib/ignite
* ~/.ignite/
* /opt/ignite/
Seems, ~/ignite/work (without a dot in the beginning) is not a Linux-way naming.
Postgresql use '/usr/local/pgsql/`
Mysql use '/var/l
Dmitriy Govorukhin created IGNITE-12102:
---
Summary: idle_verify should show info about lost partitions
Key: IGNITE-12102
URL: https://issues.apache.org/jira/browse/IGNITE-12102
Project: Ignite
I've made some changes that should help.
Can you rerun the build, please?
> On 23 Aug 2019, at 18:12, Alexey Goncharuk wrote:
>
> Who has created the task in the first place and can check why it fails? I
> see no reason to fail the release unless somebody can reasonably explain
> what exactly
Hello!
We are talking about development scenario where you have embedded database
in your project and it has to write data somewhere.
/var/lib/ignite is certainly not writable by user's development projects.
We could use ~/.config/ignite, which is pure UNIX way today, but I object
against potent
Ilya Kasnacheev created IGNITE-12103:
Summary: Change the default ignite work directory once again to
avoid writing to ~/work
Key: IGNITE-12103
URL: https://issues.apache.org/jira/browse/IGNITE-12103
Hello!
-1 (binding) for Apache Ignite 2.7.6 RC1 due to
https://issues.apache.org/jira/browse/IGNITE-12103 - let's figure out the
good default for IGNITE_WORK_DIR to avoid changing it again in future
releases.
Regards,
--
Ilya Kasnacheev
пн, 26 авг. 2019 г. в 11:42, Petr Ivanov :
> I've made s
Ilya,
> We are talking about development scenario where you have embedded database
> in your project and it has to write data somewhere.
Why it should differs from production case?
I think we should be as close to production setup as we can.
> /var/lib/ignite is certainly not writable by user's
Hello!
In development environment one can just run Java from /var/lib/ignite
(makes total sense) and will immediately get almost correct behavior (well,
data will be stored to /var/lib/ignite/ignite/work)
However, I still think that we should write to user.dir/ignite and not just
user.dir since c
Hello!
Do we still need to separate client connector configuration from thin
connector configuration from ODBC connector configuration?
I think this is a bad practice: For example, people often turn on SSL or
auth on just a subset of connectors, think they are secure, when in fact
they still have
Hello!
Also, let's not add IGNITE_ settings for options that can reasonably be
configured from IgniteConfiguration. Let's keep it for very edge cases.
Regards,
--
Ilya Kasnacheev
пн, 26 авг. 2019 г. в 12:27, Ilya Kasnacheev :
> Hello!
>
> Do we still need to separate client connector configur
Ilya,
> In development environment one can just run Java from /var/lib/ignite
Actually, I doesn't understand you.
Are you talking about development of some application that uses Ignite or
contribution to Ignite code base?
If we are talking about some application that uses Ignite then we should
Ilya, please cast your vote in the formal vote thread
https://lists.apache.org/thread.html/dab6624041507ddebe8b2d5fffdaff13bbe52d1fb481ac0d702cb4f1@%3Cdev.ignite.apache.org%3E
пн, 26 авг. 2019 г. в 12:12, Ilya Kasnacheev :
> Hello!
>
> -1 (binding) for Apache Ignite 2.7.6 RC1 due to
> https://is
Hello, Igniters.
There are a lot of variants was already proposed lets vote to one of them. I
made a list of possible paths which was mentioned earlier. I also included
variants outside of home directory('user.dir') to this list but I want to notes
that we had already discussed it and we decide
+1 for '~/.ignite/work'
пн, 26 авг. 2019 г. в 13:27, Anton Kalashnikov :
> Hello, Igniters.
>
> There are a lot of variants was already proposed lets vote to one of them.
> I made a list of possible paths which was mentioned earlier. I also
> included variants outside of home directory('user.dir'
The vote is canceled now.
Motivation:
I appreciate everyone's attention to the latest release candidate. I really
happy we were so active in voting.
Unfortunately, I really concerned about
https://issues.apache.org/jira/browse/IGNITE-12103 and I believe we should
revisit default '~/work' to show
Hello!
> In development environment one can just run Java from /var/lib/ignite
What I actually meant was 'in deployment environment' or even 'in
production environment'. Sorry for the confusion.
I really dislike the idea of ~/.ignite/work. It is a good default for
in-memory runs, but storing gig
+1 for '/var/lib/ignite'
В Пн, 26/08/2019 в 13:28 +0300, Dmitriy Pavlov пишет:
> +1 for '~/.ignite/work'
>
> пн, 26 авг. 2019 г. в 13:27, Anton Kalashnikov :
>
> > Hello, Igniters.
> >
> > There are a lot of variants was already proposed lets vote to one of them.
> > I made a list of possible p
Does this parameters intended to be overridden (for tests purposes for example)
or it will be permanently sticked to this new directory without ability to
change?
> On 26 Aug 2019, at 13:58, Nikolay Izhikov wrote:
>
> +1 for '/var/lib/ignite'
>
> В Пн, 26/08/2019 в 13:28 +0300, Dmitriy Pavlo
Yes, of course.
В Пн, 26/08/2019 в 13:58 +0300, Petr Ivanov пишет:
> Does this parameters intended to be overridden (for tests purposes for
> example) or it will be permanently sticked to this new directory without
> ability to change?
>
>
> > On 26 Aug 2019, at 13:58, Nikolay Izhikov wrote:
Hi Nikolay
> build on JDK8+
Officially Ignite does not support build (compilation) under Java version
>8. I could find a ticket if it is necessary.
There are some changes which should help to bypass IgniteLinkTaglet issue,
but I couldn't call these changes completed. You can try to enable java-9+
Hi Petr,
Thank you. now build is passing
https://ci.ignite.apache.org/viewLog.html?buildId=4537955&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum
Sincerely,
Dmitriy Pavlov
пн, 26 авг. 2019 г. в 14:03, Dmitriy Pavlov :
> Hi Nikolay
> > build on JDK8+
>
> Officially Igni
Hello, Dmitriy.
We can't create Ignite distribution from sources on jdk9+.
Is it true? Am I understand you correctly?
Should we mention it in DEVNOTES.txt or README.txt?
Do we have a ticket(umbrella ticket, IEP) to make it happen?
В Пн, 26/08/2019 в 14:03 +0300, Dmitriy Pavlov пишет:
> Hi Nikola
Ilya,
This will break backward compatibility and probably protocol, and this is
not something we should discuss in the context of this specific task. More
like this is a topic for 3.0 wishlist.
Best Regards,
Igor
On Mon, Aug 26, 2019 at 12:28 PM Ilya Kasnacheev
wrote:
> Hello!
>
> Also, let's
Yes, AFAIK, no one tested it. Each TC build uses Java 8 and then some newer
random Java for running.
Umbrella ticket:
https://issues.apache.org/jira/browse/IGNITE-11189
пн, 26 авг. 2019 г. в 14:16, Nikolay Izhikov :
> Hello, Dmitriy.
>
> We can't create Ignite distribution from sources on jdk9+.
Thanks, Dmitriy.
В Пн, 26/08/2019 в 14:18 +0300, Dmitriy Pavlov пишет:
> Yes, AFAIK, no one tested it. Each TC build uses Java 8 and then some newer
> random Java for running.
>
> Umbrella ticket:
> https://issues.apache.org/jira/browse/IGNITE-11189
>
> пн, 26 авг. 2019 г. в 14:16, Nikolay Izhik
Folks,
According to the Filesystem Hierarchy Standard [1] (Wikipedia is not
the ideal reference), the `/var/lib` directory is the `state
information. Persistent data modified by programs as they run, e.g.,
databases, packaging system metadata, etc.`
So, I'm +1 for `/var/lib/ignite` to place persi
Ok, folks, I'm not insisting on
~/ignite/work nor ~/.ignite/work
I wondering what about Windows systems. Linux is not only one platform
Ignite runs on.
пн, 26 авг. 2019 г. в 14:28, Maxim Muzafarov :
> Folks,
>
> According to the Filesystem Hierarchy Standard [1] (Wikipedia is not
> the ideal ref
Hi Igniters,
During voting on 2.7.6-rc1, I saw how experienced Ignite contributor
committer and PMC member were trying to activate cluster using control.sh
command.
We usually just call cluster().active(true), but end users have to use the
script provided in the distribution.
Related to con
Hello, Igniters.
+1 for Script help usability - issue 3
Looks like it will be great if we avoid the repeated output of the commands,
ex.:
control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
[] [--yes]
Hello!
Using /var/lib/ignite guarantees that any persistent Ignite node in
development will immediately fail with a cryptic message upon start, since
/var/lib is not writable by non-privileged users.
If our point is to force user to specify workDirectory setting, then yes,
this makes total sense.
Hello, Ilya.
We can't have discussion if you only make statements, but don't answer the
questions :)
I repeat my own statements and questions to you.
*How do you think, what is primary usage scenario for Ignite with PDS enabled
cache?*
If we are talking about some application that uses Ignite
Hello!
I think it is 2., because if a node is run from Ignite binary distribution
it has its root as a ignite work directory. I think it it another argument
for keeping data under current dir - Ignite binary distribution already
does it, why should embedded scenario be different?
In Docker age, p
Denis,
I've tried Oracle JDK 11 and OpenJDK 12 with Ignite 2.7.5, looks like:
"--add-exports=java.base/jdk.internal.misc=ALL-UNNAMED"
Is enough for running java thin client.
Also, adding:
"--add-opens=java.base/java.nio=ALL-UNNAMED"
Eliminates all warnings about illegal access (with
"--illegal-acc
Hi Alex, Would it be reasonable to migrate exports to --add-opens?
Thin clients don't use Unsafe, so --illegal-access=deny has no effect.
--illegal-acess=pertmit is also well known that it is a default value. I
guess it was added to compensate future Java defaults changes from permit
to deny. We
In Windows there is %USER%/Application Data folder (or just %USER%) that is
analog of ~/. in Linux.
MacOS has home directory as well, so that should not be a problem.
> On 26 Aug 2019, at 14:41, Dmitriy Pavlov wrote:
>
> Ok, folks, I'm not insisting on
> ~/ignite/work nor ~/.ignite/work
>
> I
AFAIK server admin expects software will store it's data in /var/ directory,
not in /home directory.
> In Docker age, packages are becoming extinct.
I don't agree with that, but seems, it's not a subject of discussion. :)
> we don't even have very good packages today
Why do you think we don't
Igniters,
I'd like to propose you to register at the ASF Slack [1] (committers seems
to be already registered) and join the Ignite channel [2].
This should simplify communication between the contributors.
P.s. I'm not saying we have to replace devlist with the Slack, but Slack is
a more suitable p
Anton,
Can we create channels for ticket, IEP discussions in ASF slack?
В Пн, 26/08/2019 в 16:09 +0300, Anton Vinogradov пишет:
> Igniters,
> I'd like to propose you to register at the ASF Slack [1] (committers seems
> to be already registered) and join the Ignite channel [2].
> This should sim
Nikolay,
Let's try ;)
On Mon, Aug 26, 2019 at 4:15 PM Nikolay Izhikov wrote:
> Anton,
>
> Can we create channels for ticket, IEP discussions in ASF slack?
>
>
> В Пн, 26/08/2019 в 16:09 +0300, Anton Vinogradov пишет:
> > Igniters,
> > I'd like to propose you to register at the ASF Slack [1] (co
Dmitry,
As I said before, thin client uses BinaryHeapOutputStream, which uses
Unsafe, so "--illegal-access=deny" has an effect.
With "--illegal-access=deny" thin client will not start unless you specify
"--add-opens=java.base/java.nio=ALL-UNNAMED"
пн, 26 авг. 2019 г. в 15:57, Dmitriy Pavlov :
>
Hi,
If we use the example of Apache Beam, usually these channels relate to a
module or language, e.g. beam-python, beam-ml, etc.
I also support the idea of ASF slack usage. Moreover, we can ask Infra to
install automatic translation of messages to English. It may help
non-native speakers to comm
I think that channels for separate IEP-s is too much.
But the slack is not indexing and not accessible for all people in the
Internet. Maybe it's wrong idea to discuss something there instead of
dev-list?
пн, 26 авг. 2019 г. в 16:27, Dmitriy Pavlov :
> Hi,
>
> If we use the example of Apache Beam
+1 for ~/.ignite/work
As Petr mentioned above, this translates well to Windows and MacOS too, we
can use "home directory" term in documentation and it works for any OS.
On Mon, Aug 26, 2019 at 4:03 PM Nikolay Izhikov wrote:
> AFAIK server admin expects software will store it's data in /var/
>
I agree with Alexey, since Dev list it better place in most cases. Apache
does not prohibit peer 2 peer communication, and ASF slack can be used as a
messenger.
The main thing here is that we (all community) clearly understand that ASF
slack is the replacement to Skype/Rocket Chat/Calls, it is not
Vladislav Pyatkov created IGNITE-12104:
--
Summary: Check deployment from cache before to load it from local
or version storage
Key: IGNITE-12104
URL: https://issues.apache.org/jira/browse/IGNITE-12104
> But the slack is not indexing and not accessible for all people in the
Internet
+1
On Mon, Aug 26, 2019 at 4:56 PM Alexey Zinoviev wrote:
>
> I think that channels for separate IEP-s is too much.
> But the slack is not indexing and not accessible for all people in the
> Internet. Maybe it's wr
Hi, Igniters!
I'm working on some metrics related aspects and it seems that we have
missed some points regarding the metrics management. There are at
least two major problems from my point of view.
Problem definition.
---
1. There is no unified approach to adding metrics
Folks, let me share more details on why Anton started the conversation
about Ignite Slack:
http://apache-ignite-developers.2346864.n4.nabble.com/The-ASF-Slack-td43233.html
Recently, a group of GridGain and Sberbank committers of Ignite has met to
discuss how to make our community more transparent
Ravil Galeyev created IGNITE-12105:
--
Summary: [ML] Implement projection vector.
Key: IGNITE-12105
URL: https://issues.apache.org/jira/browse/IGNITE-12105
Project: Ignite
Issue Type: Task
Anton,
Thanks for starting the conversation. I think that we need to explain to
our community how and why we came to this proposal. I've started another
discussion with details, sorry for not doing it earlier:
http://apache-ignite-developers.2346864.n4.nabble.com/Making-Ignite-Collaboration-100-Op
Hi Denis,
I really like the initiative for transparency and collaboration. Are there
any plans to help get new contributors up to speed with the project where
they can contribute effectively? Sometimes it can be intimidating to start
on a large project without some help or advice. Maybe assigning
Igniters,
I can't disagree with Nikolay that, as a database, Ignite needs to persist
changes to a folder different from "user.home" one. But with the current
rate of project growth and adoption, I would encourage us to eliminate any
possible obstacles a user might come across during the getting st
Denis Magda created IGNITE-12106:
Summary: Rework ignite binary metadata exception for ease of
troubleshooting
Key: IGNITE-12106
URL: https://issues.apache.org/jira/browse/IGNITE-12106
Project: Ignite
Dmitry,
As long as the vote has been canceled and we're going to do several
improvements before starting a new one, I'd like to ask your permission to
include this ticket in 2.7.6 scope:
https://issues.apache.org/jira/browse/IGNITE-12106
It suggests the changes in log messages to simplify "binary
Denis Magda created IGNITE-12107:
Summary: Docs: request setting IGNITE_HOME to permanent location
in Docker
Key: IGNITE-12107
URL: https://issues.apache.org/jira/browse/IGNITE-12107
Project: Ignite
Ivan, thanks for sharing your thoughts.
Created a ticket for the error message improvement
https://issues.apache.org/jira/browse/IGNITE-12106
and doc changes:
https://issues.apache.org/jira/browse/IGNITE-12107
Will try to make it to Ignite 2.7.6.
-
Denis
On Fri, Aug 23, 2019 at 3:05 PM Павлу
Absolutely, error messages are the most important guidance for users, I see
no reason to reject.
пн, 26 авг. 2019 г. в 23:26, Denis Magda :
> Dmitry,
>
> As long as the vote has been canceled and we're going to do several
> improvements before starting a new one, I'd like to ask your permission t
61 matches
Mail list logo
