Hello Nikolay,
Your proposal sounds reasonable. However, I would suggest us to wait while
partition-awareness is supported for Java thin client first. With that
feature, the client can connect to any node directly while presently all
the communication goes through a proxy (a node the client is
GitHub user sergey-nbl opened a pull request:
https://github.com/apache/ignite/pull/5043
ignite-9951: thin php: Date data type cut nanos
- Fixed Date::fromDateTime and Date::toDateTime to support millis.
You can merge this pull request into a Git repository by running:
$ git
Guys,
>From my experience, Ignite and Spark clusters typically run in the same
environment, which makes client node a more preferable option. Mainly,
because of performance. BTW, I doubt partition-awareness on thin client
will help either, because in dataframes we only run SQL queries and I
Hi Anton,
I ran a problematic build against my contribution [1] and it seems to pass
fine. Then I ran the build against your PR branch and it hanged [2].
There is nothing surprising that it fired only in master because the build
was added to RunAll after your PR runs.
Could you please take a
Nikolay,
Where do you track those 8 blockers? Can't find them on this wiki page:
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7
--
Denis
On Sat, Oct 20, 2018 at 11:31 AM Nikolay Izhikov
wrote:
> Hello, Denis.
>
> As a first time release manager I'm trying to rely on
Hi Igniters,
On Friday I felt a real inconvenience (pain in ass) with running builds for
a ticked I worked on [1]. There were two the most frustrating moments:
1. Estimated build completion time was 11 hours after the start.
2. There are newly added suites which are failing constantly in recent
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
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
Andrey Kalinin created IGNITE-9954:
--
Summary: An error in rolling back the transaction caused the
cluster to hang
Key: IGNITE-9954
URL: https://issues.apache.org/jira/browse/IGNITE-9954
Project:
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
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
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
+1 for all proposals.
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
Hello, Denis.
As a first time release manager I'm trying to rely on Ignite veterans opinion.
Guys told me that we must fix all blockers and only after it make the release.
Let's fix them all.
What do you think?
> When are we sending a release candidate for vote?
When all blocker bugs will be
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
Oh, nice
Thanks for quick response
I've check against JS and PHP, now its works properly
Igor, can you approve this patch?
сб, 20 окт. 2018 г. в 0:57, Dmitry Melnichuk :
> Stepan,
>
> My bad. I got the Decimal part of Ignite thin client protocol
> specification totally wrong.
>
> Just
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/5042
Investigation: Queries (Binary Objects Simple Mapper)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite investigation1
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
Hello, Igniters.
Currently, Spark Data Frame integration implemented via client node connection.
Whenever we need to retrieve some data into Spark worker(or master) from Ignite
we start a client node.
It has several major disadvantages:
1. We should copy whole Ignite distribution on to
20 matches
Mail list logo
