f should improve the part of issues from above, but
> definitely, sorting by document score at least should be implemented along
> with limit.
>
> This is a pretty short commentary if you still have any questions, please
> ask, do not hesitate)
>
> BR,
> Yuriy Shuliha
>
> чт, 19
Hi Maria,
Yes, it should work with your classes. It worth noting, that
"lastName" will be accessible in your queries, "SELECT lastName FROM
..." should work. Note that you should use simply "lastName" in SQL
but not "general.lastName".
By the way, usually it is better to write such questions to
Anton, folks,
Out of curiosity. Do we have some measurements of PME execution in an
environment similar to some real-world one? In my mind some kind of
"profile" showing durations of different PME phases with an indication
where we are "blocked" would be ideal.
ср, 18 сент. 2019 г. в 13:27,
Yuriy,
Greatly appreciate your interest.
Could you please elaborate a little bit about sorting? What tasks does
it help to solve and how? It would be great to provide an example.
ср, 18 сент. 2019 г. в 09:39, Alexei Scherbakov :
>
> Denis,
>
> I like the idea of throwing an exception for
Anton,
Thank you very much for performing the discussion! I found it pretty
much useful. And I really like such kind of collaboration and hope
that we will go forward in that direction.
Looking forward for meeting minutes and slides.
вт, 10 сент. 2019 г. в 10:24, Alexey Goncharuk :
>
> Anton,
>
Maxim, my congratulations!
2019-08-29 7:25 GMT+11:00, Andrey Kuznetsov :
> Great news! Congratulations!
>
> ср, 28 авг. 2019 г., 18:28 Alex Plehanov :
>
>> Maxim, congratulations!
>>
>> ср, 28 авг. 2019 г. в 18:13, Nikita Amelchev :
>>
>> > My congratulations, Maxim!
>> >
>> > ср, 28 авг. 2019 г.
+ Meeting minutes
2019-08-28 22:29 GMT+11:00, Alexey Zinoviev :
> I am totally support the idea with the planned and widely announced Hangout
> meeting between commiters and contributers and posting the link to the
> dev-list with the special Topic Name and short agenda. Maybe, the recorded
>
Ilya,
2 points:
1. It is a good point that a directory name "work" in arbitrary place
can cause a lot of confusion.
2. As far as I got, default directory is not in e.g. /home/username
but in one pointed by "user.dir" system property which is a directory
where a java process started (if property
Denis,
Actually binary metadata is not stored in a metastore (however there
were a discussion about moving it). User scenario is valid. A
meaningful exception and documentation are good.
And also I can think about revisiting a needed configuration for
persistence in containerized environments.
SqlFieldsQuery and
>> SqlQuery.
>>
>>
>> Regards,
>>
>> Saikat
>>
>>
>>
>> On Thu, Aug 15, 2019 at 6:13 AM Павлухин Иван
>> wrote:
>>
>>> Saikat, Denis,
>>>
>>> I left comments in the ticket [1].
hout conflicts, just push it.
> >
> > If it contains conflicts it is better to push to 2.7.6-based branch and
> > start additional run-all, example
> > https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
> > base: 2.7.6
> >
> > Si
t; > > > > Hi al,, i also suggest to append [1], cause it could
> > >> produce
> > >> >> > > > > > > > CorruptedTreeException in some scenario.
> > >> >> > > > > > > >
> &g
; > > > > > > > https://issues.apache.org/jira/browse/IGNITE-11953
> > > > > > > > > > >
> > > > > > > > > > > Plus, I would upgrade our Spark integration to version
> > 2.4
> > > as
> > > > >
> > > &
ache/ignite/pull/6490/files
> > >
> > > I wanted to discuss if it is correct intended usage of Default Query
> > > Timeout or should we reconsider?
> > >
> > > Regards,
> > > Saikat
> > >
> > >
> > >
> > > On Fr
Just to keep history connected. The discussion continued in
http://apache-ignite-developers.2346864.n4.nabble.com/SQL-query-timeout-in-progress-or-abandoned-td42964.html
вт, 18 июн. 2019 г. в 12:22, Павлухин Иван :
>
> Hi Saikat,
>
> Thank you for driving it. I left my comments [1].
&
ponses dedicated thread is used.
> > In a draft implementation of IGNITE-11685 I've used another approach: each
> > request thread can read a response (if lock is acquired by this thread
> > successfully) and complete a future of its own request or another threads
> > re
Denis,
Several clarifying questions:
1. Do you have an idea why metadata registration takes so long? So
poor disks? So many data to write? A contention with disk writes by
other subsystems?
2. Do we need a persistent metadata for in-memory caches? Or is it so
accidentally?
Generally, I think
;>>> Surefite documentation [1] says:
> >>>> If forkCount=0, it's impossible to use the system class loader or a
> >>>> plain old Java classpath; we have to use an isolated class loader.
> >>>>
> >>>> When using isolated
s during node start.
> > But we still don't have any real examples that require more flexibility
> > than labels have.
> >
> > вт, 6 авг. 2019 г. в 14:46, Павлухин Иван :
> >
> > > Alexey,
> > >
> > > It seems that a problem has a solution wi
Folks,
I asked about TC infrastructure problems before and did not get
answers. Does any of you know how to fix problems of that sort? Should
not the process be transparent for a community members?
пн, 12 авг. 2019 г. в 11:00, Dmitriy Pavlov :
>
> I also see some issues with 2.7.6 testing.
I'd prefer to leave the current situation with Javadoc as it is and
> > just to ask to apply the patch [1][2]. Can you? :-)
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-12051
> > [2] https://github.com/apache/ignite/pull/6760
> >
> > On Thu, 8 Aug 2019 at
Ilya, Pavel,
Do we a have a proposal how to fix the root cause of the problem?
Should we a have a ticket for it?
ср, 7 авг. 2019 г. в 17:48, Ilya Kasnacheev :
>
> Hello!
>
> I think we should definitely stop running futures out of striped pool,
> while holding any cache logs (stripe thread
Just for the protocol. There was an original dev-list discussion [1].
Added a link to the ticket as well.
[1]
http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-7285-Add-default-query-timeout-td41828.html
пт, 9 авг. 2019 г. в 01:22, Denis Magda :
>
> Hey Saikat,
>
> Are you still
> What's the scope for this release?
Same question.
On the other hand an idea of 2.7.6 release attracts me because having
a practice of doing frequent minor releases can help us to build
reliable and predictable release rails.
чт, 8 авг. 2019 г. в 15:09, Ilya Kasnacheev :
>
> Hello!
>
> What's
D = 0L;
> > > > or
> > > > /** */
> > > > @LoggerResource
> > > > private IgniteLogger log;
> > > >
> > > > There are more than 8000 lines of /** */ only at the ignite-core
> > module (do
> > > > not include tests
Denis,
Could you please provide more details why do we need to run these
tests in forked JVM?
Still, having separate security suite on TC sounds not bad.
ср, 7 авг. 2019 г. в 09:35, Vyacheslav Daradur :
>
> Hi Denis.
>
> I think it is fine to extract security tests in a separate build plan on
Ilya,
I am not sure that enabling subset of events will fit all needs. If we
would like to do so then it might be good idea to make it clear in API
that certain events are enabled by default (e.g. put them into
separate class).
Also we should be careful with backward compatibility, some kind of
Hi,
Denis, thank you for starting this discussion!
My opinion here is that having a good javadoc for every class and
method is not feasible in the real world. I am quite curious to see a
non-trivial project which follows it. Also, all comments and javadocs
are prone to become misleading when
Ilya, my congratulations!
вт, 6 авг. 2019 г. в 23:12, Dmitriy Pavlov :
>
> Ilya, congratulations!
>
> вт, 6 авг. 2019 г. в 22:58, Denis Magda :
>
> > The Project Management Committee (PMC) for Apache Ignite
> > has invited Ilya Kasnacheev to become a committer and we are pleased
> > to announce
Andrey,
It seems that screenshot was rejected, I do not see it.
вт, 6 авг. 2019 г. в 15:07, Andrey Gura :
>
> Good example of proper buckets configuration. Such configuration is
> suitable for may cases. See attached screenshot (I hope it will not be
> reject by mail system or forum).
>
>
> On
Alexey,
It seems that a problem has a solution with using 2 attributes or 2
labels. Is not it more clear than using custom code?
Folks,
> I don't think we should take "hard to implement" as an argument in this
> discussion :)
Did not fully get the point. KISS principle is not true anymore? Or
Hi Nikolay,
Could you please elaborate how will NodeAttributeFilter behave? Do you
mean specifying attribute name and value for exact comparison inside?
Without any dynamic (user) code involved?
Also I it is quite interesting for me what flexibility you are
thinking about? I think that the topic
the update on my PR, I didn't merge
> > > for
> > > >> a 3
> > > >> > > months and doesn't know that rules were changed
> > > >> > > Please, revert my commit, I will update my PR according CheckStyle
> > > job
> > >
Alexey,
Actually the commit [1] is very suspicious:
1. Commit message "[ML] Hyper-parameter tuning via Genetic Algorithm
(#6713)" does not refer to a ticket.
2. Is there a ticket? Consequently it is not easy to understand what
was done and check ticket according to regular flow (review, TC run).
reduces the discontent and outrage of community
> > > > members (if you reduce to 2-6 weeks it could be intersected with human
> > > > events of most part of contributors like vacation, birthdays, wedding,
> > spam
> > > > filters and etc.), believe me (I h
& Apache
> > accounts.
> > https://gitbox.apache.org/setup/
> >
> > чт, 25 июл. 2019 г. в 11:17, Nikolay Izhikov :
> >
> > > Yes.
> > >
> > > Do someone have permission to close my(or any other contributor) PR to
> > > apache/ignite?
&
NIkolay,
Do you mean technical ability?
чт, 25 июл. 2019 г. в 10:33, Nikolay Izhikov :
>
> Hello, Ivan.
>
> Do we have the ability to close PRs from other contributors?
>
> В Чт, 25/07/2019 в 09:12 +0300, Павлухин Иван пишет:
> > Igniters,
> >
> > I would l
ojects
> >
> > Apache Kafka - 533 PR opened.
> > Apache Spark - 484 PR opened.
> > Apache Flink - 430 PR opened.
> >
> > В Вт, 11/12/2018 в 09:24 +0300, Pavel Tupitsyn пишет:
> >> Agree with Dmitriy.
> >>
> >> We use GitHub PRs in our wor
gt;
> +1 for moving from RunAll to RunAllNighlty
>
> пн, 22 июл. 2019 г. в 12:21, Павлухин Иван :
>
> > Igniters,
> >
> > As you know Ignite RunAll on TC takes significant resources. I noticed
> > that build job "Queries (Binary Objects Simple Mapper)"
Igniters,
As you know Ignite RunAll on TC takes significant resources. I noticed
that build job "Queries (Binary Objects Simple Mapper)" [1] actually
duplicates "Queries 1" [2] job and the same test set using simple name
mapper for binary objects. I suppose that we can exclude it from daily
ns will be definitely removed.
>
>
> ср, 17 июл. 2019 г. в 15:26, Павлухин Иван :
>
> > Also, I did not quite get the point about JSR107 (JCache). From time
> > to time I see on user-list threads where Ignite is used along with
> > Spring annotation-based cache integration
e no need for
> such mark.
> So, let's assume it's production-ready until another state is not confirmed
> :)
>
> [1] https://docs.oracle.com/javase/9/docs/api/jdk/jfr/Experimental.html
>
> On Thu, Jul 18, 2019 at 4:56 PM Павлухин Иван wrote:
>
> > Folks
Folks,
Sorry, I was not very attentive. Could you please clarify whether (or
not) this feature is currently in an experiment state? And a couple of
obvious things:
1. If it is experimental it should be clear for a user (e.g. from javadoc).
2. If not all limitations should be described in javadocs
FYI,
Build configuration PdsIndexingWalRecovery was removed.
ср, 17 июл. 2019 г. в 14:31, Павлухин Иван :
>
> Yet another candidate
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_QueriesOom?branch=pull%2F4611%2Fhead=overview
>
> ср, 17 июл. 2019 г. в 14:06
, Павлухин Иван :
>
> Folks,
>
> Sorry if I am repeating something. I checked a page [1] and have not
> found several items.
> 1. I thought that there was an agreement of dropping OLD service grid,
> was not it?
> 2. Also IndexingSpi seems to me as a candidate for removal.
>
Folks,
Sorry if I am repeating something. I checked a page [1] and have not
found several items.
1. I thought that there was an agreement of dropping OLD service grid,
was not it?
2. Also IndexingSpi seems to me as a candidate for removal.
Should I add those items to the page? Or is there
Yet another candidate
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_QueriesOom?branch=pull%2F4611%2Fhead=overview
ср, 17 июл. 2019 г. в 14:06, Павлухин Иван :
>
> Here is a closed PR [1]. Let's drop that run-config [2].
>
> [1] https://github.com/apache/ignite/pul
Here is a closed PR [1]. Let's drop that run-config [2].
[1] https://github.com/apache/ignite/pull/4239/files
[2]
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PdsIndexingWalRecovery?branch=%3Cdefault%3E=overview
чт, 21 мар. 2019 г. в 17:53, Petr Ivanov :
>
> According to
Hi,
Does anyone know what is the purpose of job PDS (Indexing / WAL &
Recovery) [1]? It refers to non-existing
IgnitePdsWithIndexingWalAndRecoveryTestSuite class and runs no tests.
Can we delete it safely?
[1]
code for details:
>
> if (invalidNodeSet.contains(affNode) || !cctx.discovery().alive(affNode)) {
> onDone(Collections.emptyMap()); // Finishing mini future with just "ok".
>
> On Tue, Jul 16, 2019 at 9:04 AM Павлухин Иван wrote:
>
> > Anton,
> >
> > You referenced to
ve this issue, but it
> > seems to be an overcomplicated way.
> > The main question there, it there any simple way?
> >
> >>> checking read from backup will just wait for commit if it's in progress.
> > Agree, but seems there is no need to acquire the lock, w
Hi,
Currently I see that there many failed TC jobs in recent RunAll [1]. I
checked logs of couple of them and it seems that it is related to no
free disk space on agents, e.g. [2].
1. Who can resolve it?
2. How can it be resolved?
3. How to avoid similar issues in future?
[1]
lucky txB writes a value 2 for the key on primary and
> > backup.
> > AFAIK, reordering not possible since backups "prepared" before primary
> > releases lock.
> > So, consistency guaranteed by failover and by "prepare" feature of 2PC.
> > Se
Anton,
Is such behavior observed for 2PC or for 1PC optimization? Does not it
mean that the things can be even worse and an inconsistent write is
possible on a backup? E.g. in scenario:
1. txA writes a value 1 for the key on primary.
2. txA unlocks the key on primary.
3. txA freezes before
Merged the patch to master [1]. Thank Alex Plekhanov for a review.
[1] https://issues.apache.org/jira/browse/IGNITE-11951
ср, 10 июл. 2019 г. в 08:42, Павлухин Иван :
>
> Hi,
>
> I made some small improvements in JdkMarshaller [1]. I will be happy
> if someone reviews it. Ch
I merged the patch [1] by lazy consensus.
[1] https://issues.apache.org/jira/browse/IGNITE-11946
пн, 8 июл. 2019 г. в 20:48, Павлухин Иван :
>
> Igniters,
>
> I present a ticket [1] removing java.transaction and java.corba
> modules from sh/bat scripts for your review. I remin
>
> > Ivan.
> >
> > > I suppose that I did not ever claim such thing
> >
> > Thanks for clarifing :)
> >
> >
> > > GitHub project outside any commercial company accounts, there all Apache
> > committers added as collaborators may work.
>
rsion of H2 fork.
> > Then we could modify the fork in any time without compatibility issues.
> > When new feature is ready to use by Ignite need to modify code of Ignite
> > and change dependency version for H2 fork.
> > However H2 for in the case should be release more often t
The question is - *Who can apply those changes*.
>
> I think all Ignite commiters should have write priveledges to H2 fork.
>
> В Ср, 10/07/2019 в 11:30 +0300, Павлухин Иван пишет:
> > Folks,
> >
> > I would like to highlight a couple of points.
> > 1. Perhaps it
Folks,
I would like to highlight a couple of points.
1. Perhaps it is not so crucial where is this fork located if the code
is publicly available and can be cloned to another repository easily.
We can relocate code and use it at any point in future.
2. Anyways some process must be established for
Hi,
I made some small improvements in JdkMarshaller [1]. I will be happy
if someone reviews it. Changes are quite simple.
[1] https://issues.apache.org/jira/browse/IGNITE-11951
--
Best regards,
Ivan Pavlukhin
://issues.apache.org/jira/browse/IGNITE-11946
ср, 3 июл. 2019 г. в 21:40, Павлухин Иван :
>
> I removed command line arguments enabling java.transaction and
> java.corba module from TC configuration. All activity in a ticket [1].
>
> [1] https://issues.apache.org/jira/browse/IGNITE-11946
>
Ivan,
I think that it is a really good that you found those not tested
examples. Thank you!
пт, 5 июл. 2019 г. в 11:31, Павлухин Иван :
>
> Ivan,
>
> I uncommented all tests referring to IGNITE-711 [1] in
> BasicExamplesSelfTest and all they passed.
>
> Generally, exa
@Test annotation. It is some kind of rollback to JUnit3
> > syntax.
> >
> > Anton,
> > thank you for the reminder, I will update IEP according to the
> > conversation.
> >
> > [1] https://www.baeldung.com/junit5-dynamic-tests
> >
> > вт, 26 фев
=buildTypeHistoryList_IgniteTests24Java8=%3Cdefault%3E
ср, 3 июл. 2019 г. в 14:46, Павлухин Иван :
>
> Ilya, Dmitriy,
>
> Are we going to drop only compilation on Java 9 and 10 but continue
> running tests on all versions (8-11)? The idea sounds ok to me. But to
> be honest I must
Seems to be an interference of two commits related to continuous
queries [1, 2]. In one a test was added and the test was broken by
another commit.
Ivan, Denis, could please take a look?
[1]
https://github.com/apache/ignite/commit/db74e92dcd56bc5a45ed9d3a382be8bcfa2a76dc
[2]
I removed command line arguments enabling java.transaction and
java.corba module from TC configuration. All activity in a ticket [1].
[1] https://issues.apache.org/jira/browse/IGNITE-11946
вс, 30 июн. 2019 г. в 07:31, Павлухин Иван :
>
> I made 2 experiments:
> 1. Removed --ad
witch maven.compiler.target to 11 when using Java 9+
> > in maven.compiler.target? Indeed it breaks compilation on Java 9-10. This
> > is in IGNITE-11189
> >
> > BTW they are unsupported now, maybe we just drop them for good? Ivan what
> > do you think?
> >
> &
r.java#L41
> [2] https://issues.apache.org/jira/browse/IGNITE-11927
>
>
> В Пн, 01/07/2019 в 15:39 +0300, Павлухин Иван пишет:
> > Nikolay, Igniters,
> >
> > In my mind there are several configuration aspects:
> > 1. Specifying subset of metrics which are exported to a
.
What do you think?
вт, 2 июл. 2019 г. в 16:58, Ilya Kasnacheev :
>
> Hello!
>
> I have just tried, looks like it is buildable with Java 12 (provided that
> -Dmaven.javadoc.skip=true is specified)
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 1 июл. 2019
bjections?
>
>
> > 3. Will we adress implementing Java 9+ modules during that process?
>
>
> I think this should be optional. Do you think we need to do it in the
> first instance?
>
> -
> Denis
>
>
> On Sun, Jun 30, 2019 at 10:45 PM Павлухин Иван wrote:
>
&g
Sorry for that. Now everything works completely fine for me. Seems to
be some surprise from my ISP.
вт, 2 июл. 2019 г. в 09:18, Павлухин Иван :
>
> Igniters,
>
> Currently TC web UI is not loaded in my environment and reports
> ERR_CONNECTION_TIMED_OUT. Is the problem on my sid
Igniters,
Currently TC web UI is not loaded in my environment and reports
ERR_CONNECTION_TIMED_OUT. Is the problem on my side or is TC down?
--
Best regards,
Ivan Pavlukhin
Hi,
SpiUriDeploy fails on TC when it is run with any Java 9+ version [1].
The reason is very simple, it contains one preliminary build step
which is forced to run with Java 8. But for Java 9+ builds we pass
module-related arguments and consequently it leads to Java 8 failure
(unknown argument). I
Nikolay, Igniters,
In my mind there are several configuration aspects:
1. Specifying subset of metrics which are exported to an external system.
2. Subset of metrics which is collected (enable/disable sensor).
3. A particular metric (sensor) parameters.
Are we going to address all points in the
Hi Denis,
I fully support the idea. Could you please clarify on following points:
1. I did not get from IEP whether Thin Clients have a separate
repository and a release lifecycle or not.
2. Are we going to exclude tests for unsupported modules from Ignite TeamCity?
3. Will we adress implementing
. If there is no objections I
will cleanup that option from TC configurations and Ignite scripts.
[1] https://issues.apache.org/jira/browse/IGNITE-9687
пт, 28 июн. 2019 г. в 10:09, Павлухин Иван :
>
> Folks,
>
> During investigation of thin client test suite failures [1] I found
> that it is no
VM_EXTRA_ARGS%, simpy
speaking "~Build Apache Ignite~" JVM_EXTRA_ARGS value is borrowed.
"~Build Apache Ignite~" configures that parameter in a build step
"Setup additional arguments" by running a special command line script,
args are chosen depending on Java vers
Folks,
During investigation of thin client test suite failures [1] I found
that it is not clear whether --add-modules=java.transaction in
ignite.sh/bat is needed (we add this module for Java 9 and 10). In
thread [1] I already mentioned that launching ignite.sh with Java 9
and ignite-jta libraries
to resolve some needed classes). I will start
a separate thread related to JTA module.
пт, 21 июн. 2019 г. в 14:46, Павлухин Иван :
>
> My next question is why do we need adding java.transaction module
> explicitly for Java 9 and 10? As I see since 11 version there is no
> such module and
Hi Nikolay, Alex,
A couple of my humble comments
> Aggregation should be done with the metric collect system(Prometheus,
> Graphite, etc.).
I like that statement very much!
> But, what if a user doesn't use any external monitoring system and wants to
> know the health of Ignite instance?
I
. It is complicated...
чт, 20 июн. 2019 г. в 17:13, Павлухин Иван :
>
> Igniters,
>
> I found one thing which might be reason of an observed behavior. The
> problem does not appear for maven-based tests, while e.g. Python thin
> client tests use ignite.sh for starting a cluster.
95 is (intentionally) vague. Will separate notification
> > based on JDK version be supported or not, depends on the time available to
> > complete this task.
> >
> > чт, 20 июн. 2019 г. в 12:02, Павлухин Иван :
> >
> > > Dmitriy,
> > >
> > > It is g
> based on JDK version be supported or not, depends on the time available to
> complete this task.
>
> чт, 20 июн. 2019 г. в 12:02, Павлухин Иван :
>
> > Dmitriy,
> >
> > It is good to know that TC Bot is being developed actively. Just to
> > double check. Wi
ild run history faster than it is now.
>
> Only nightly runs are random, and yes, Ignite is tested using different VMs
> because Ignite 2.7.5 declared support of, at least, Java 11.
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 19 июн. 2019 г. в 22:13, Павлухин Иван :
>
> > M
For curious ones I copied a RunAll DSL configuration to gist [1].
[1] https://gist.github.com/pavlukhin/e788bbebafe69ce9d9a3c9e9871ab8c4
чт, 20 июн. 2019 г. в 08:42, Павлухин Иван :
>
> Dmitriy,
>
> It is a very important topic for Ignite CI. I think it would be great
> if
Dmitriy,
It is a very important topic for Ignite CI. I think it would be great
if all significant changes in a build configuration goes with a
meaningful description (a commit message). As for me, DSL sounds
promising.
BTW, a special rights are needed to view
+1
чт, 20 июн. 2019 г. в 04:18, Valentin Kulichenko
:
>
> +1
>
> On Wed, Jun 19, 2019 at 5:58 PM Roman Shtykh
> wrote:
>
> > +1
> >
> >
> > On Thursday, June 20, 2019, 7:34:47 a.m. GMT+9, Andrey Gura <
> > ag...@apache.org> wrote:
> >
> > +1
> >
> > On Thu, Jun 20, 2019 at 12:58 AM Denis
versions nightly builds?
>
> On Wed, 19 Jun 2019 at 13:47, Павлухин Иван wrote:
> >
> > Dmitriy,
> >
> > Thank you for the hint! Java version seems to be the reason. I see
> > that tests pass with Java 8 and 11 and fail with Java 10. See the
> > except
/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
... 18 more
вт, 18 июн. 2019 г. в 23:27, Dmitriy Pavlov :
>
> Hi Ivan,
>
> Can these failures be related to Java version? Java home is set randomly by
> TC Bot.
>
> Dmitriy Pavlov
>
> вт, 18 июн. 2019 г. в 22:11, Павлух
Hi igniters,
Does anyone know why python, php and nodejs [1, 2, 3] suites fail so
frequently on TC? Is there any activity to deal with it?
[1]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ThinClientPython_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
[2]
Do we still need onheap caches?
вт, 18 июн. 2019 г. в 21:30, Denis Magda :
>
> +1
>
> Thick (aka. standard clients) provide comprehensive compute APIs with
> peer-class-loading. That's a huge differentiator for Ignite. Until thin
> clients support compute and ML API at the same level as the
Nikolay, Dmitriy,
Should we have a separate thread devoted to client nodes?
Also, my cent here is from a Hazelcast history. Once they removed
their thick client (called LiteMember), but after a while they brought
it back. I think we need to learn this lesson in more details.
вт, 18 июн. 2019 г.
gt;> Andrey K.,
> > >>
> > >>> I think we should develop some kind of "Queries" options on Ignite
> > >>> configuration.
> > >>
> > >> Quite a reasonable idea. We already have couple of query-related
> > >> properties
Denis,
I must say that aforementioned solutions for a Hadoop ecosystem appear
from time to time in questions on a user mailing list. So, it seems
that there is a practical need for such solutions.
But of course it does not mean that we should continue a support of
IGFS and Hadoop Accelerator. If
> >>> On 12 Jun 2019, at 21:54, Nikolay Izhikov wrote:
> >>>
> >>> +1 for including checkstyl to "Build Apache Ignite".
> >>>
> >>> В Ср, 12/06/2019 в 21:29 +0300, Павлухин Иван пишет:
> >>>> Maxim,
> >>&g
, 31 янв. 2019 г. в 21:30, Dmitriy Pavlov :
> >>
> >> > Sure, I don't see any issues with using the default style. It is
> >> > definitely better than broken CSS.
> >> >
> >> > Thank you for accurate & detailed research.
> >> &
Maxim,
Options 1 and 3 sounds fine to me. And taking into account current
state I tend to think that option 1 is even better.
вт, 11 июн. 2019 г. в 14:19, Maxim Muzafarov :
>
> Dmitry,
>
> Thank you.
> Sure, I'll not change anything on TC without discussion with all the
> community.
>
> On Tue,
versions it looks like some
> previously built artefacts have been cashed in Maven local repository.
>
> On Fri, Jun 7, 2019 at 9:45 AM Павлухин Иван wrote:
> >
> > Vyacheslav,
> >
> > > Ivan, try to clean local repo (~/m2) and rebuild the project once again
&
019 г. в 22:37, Vyacheslav Daradur :
>
> > +1 from me. Built from sources and run several examples.
> >
> > Ivan, try to clean local repo (~/m2) and rebuild the project once
> > again according to DEVNOTES.txt
> >
> > On Thu, Jun 6, 2019 at 7:37 PM Павлухин
1 - 100 of 322 matches
Mail list logo
