Vladimir Ozerov created IGNITE-7806:
---
Summary: SQL TX: Backup update protocol
Key: IGNITE-7806
URL: https://issues.apache.org/jira/browse/IGNITE-7806
Project: Ignite
Issue Type: Task
Vladimir Ozerov created IGNITE-7807:
---
Summary: SQL TX: Store lock info inside tuples
Key: IGNITE-7807
URL: https://issues.apache.org/jira/browse/IGNITE-7807
Project: Ignite
Issue Type: Task
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3566
---
Peter Ivanov created IGNITE-7808:
Summary: Automate Docker images build
Key: IGNITE-7808
URL: https://issues.apache.org/jira/browse/IGNITE-7808
Project: Ignite
Issue Type: Improvement
Dmitriy Pavlov created IGNITE-7809:
--
Summary: Ignite PDS 2 & PDS 2 Direct IO: stable failures of
IgniteWalFlushDefaultSelfTest
Key: IGNITE-7809
URL: https://issues.apache.org/jira/browse/IGNITE-7809
Hi to all.
I have done issue ignite-7640. Please review.
JIRA: https://issues.apache.org/jira/browse/IGNITE-7640
PR: https://github.com/apache/ignite/pull/3515
TC:
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&branch_IgniteTests24Java8=pull%2F3515%2Fhead
CR: https://rev
Ilya Borisov created IGNITE-7810:
Summary: Web console: replace Roboto slab font with Roboto regular
Key: IGNITE-7810
URL: https://issues.apache.org/jira/browse/IGNITE-7810
Project: Ignite
Is
Hi all,
I'm triyng to clarify for myseft issue [1] of rewriting this test case to
use multiple JVMs. I'm trying to reproduce it using steps described here
[2]:
As I correct understand issue description, I'm runing testJobIdCollision
and expecting to get exception:
"Received computation request wit
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/3568
Removed default data region creation for client nodes.
Added meaningful exception if there's no data region for the cache.
You can merge this pull request into a Git repository by running:
Hello Igniters!
Currently we have suspension/resuming implemented for optimistic
transactions [1].
Unless suspend/resume isn't supported for pessimistic tx JTA isn't fully
supported [4].
I’m working on a ticket "Suspension/resuming for pessimistic transactions"
[2].
Goal of the ticket is to suppo
My 50 cents:
1) Agree with Pavel, not need to deserialize at all
2) May be you see everything in the upper case because this is how CREATE
TABLE works - every object name (table name, column name, etc.) are
converted to upper case by default. This is expected behavior of every SQL
engine. If you wa
Hi Nikolay,
Are there any news about these tests apperance in suites?
It seems I've found one more example in
https://ci.ignite.apache.org/viewLog.html?buildId=1106598&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_IgniteOSGi
(other
change PR run). I'm not sure that OSGI build configuration i
Hello, Dmitriy.
I'm investigate issue and share results later today.
В Пн, 26/02/2018 в 11:31 +, Dmitry Pavlov пишет:
> Hi Nikolay,
>
> Are there any news about these tests apperance in suites?
>
> It seems I've found one more example in
> https://ci.ignite.apache.org/viewLog.html?buildId=1
Vova, Alexey
3) The exception is not enough for that case. We should return a proper
error message in the json reply.
On Mon, Feb 26, 2018 at 2:20 PM, Vladimir Ozerov
wrote:
> My 50 cents:
> 1) Agree with Pavel, not need to deserialize at all
> 2) May be you see everything in the upper case bec
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/3552
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3502
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3492
---
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/3569
IGNITE-7809 : Fixed tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7809
Alternatively you can review an
Igor Sapego created IGNITE-7811:
---
Summary: ODBC: Implement connection fail over
Key: IGNITE-7811
URL: https://issues.apache.org/jira/browse/IGNITE-7811
Project: Ignite
Issue Type: Bug
Vova, Pavel, Sergey,
Thanks for you comments.
1) There one corner case with POJO objects in cache.
Binary marshaler convert by fields, not by getters. So if you have
class Person {
private int orgId;
...
public int getOrganizationId() {...}
}
POJO will be transformed to {"organizationId":
Github user nizhikov closed the pull request at:
https://github.com/apache/ignite/pull/2773
---
Alexey Goncharuk created IGNITE-7812:
Summary: Slow rebalancing in case of enabled persistence
Key: IGNITE-7812
URL: https://issues.apache.org/jira/browse/IGNITE-7812
Project: Ignite
Issu
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite/pull/3570
Introduce scala-test profile to hide scalatest-maven-plugin.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nizhikov/ignite scala-test-profil
Hello, Dmitriy.
scalatest-maven-plugin doesn't handle "test" property.
So when "scala" profile enabled it will execute all Scala Spark tests for any
test plan.
I propose to hide scalatest plugin declaration into profile "scala-test" [1]
And enable it only for specific team city plans.
I.e "Igni
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/3571
IGNITE-7531: Implemented copy, insert, batched insert benchmarks
https://issues.apache.org/jira/browse/IGNITE-7531
You can merge this pull request into a Git repository by running:
$ g
I agree.
Alexey K, what do you think?
Sincerely,
Dmitriy Pavlov
пн, 26 февр. 2018 г. в 19:17, Nikolay Izhikov :
> Hello, Dmitriy.
>
> scalatest-maven-plugin doesn't handle "test" property.
> So when "scala" profile enabled it will execute all Scala Spark tests for
> any test plan.
>
> I propose
Pavan Jadda created IGNITE-7813:
---
Summary: Method
org/apache/ignite/cache/hibernate/HibernateRegionFactory.start(Lorg/hibernate/boot/spi/SessionFactoryOptions;Ljava/util/Properties;)V
is abstract
Key: IGNITE-7813
Anton Kalashnikov created IGNITE-7814:
-
Summary: Lost scala211.library.version parameter
Key: IGNITE-7814
URL: https://issues.apache.org/jira/browse/IGNITE-7814
Project: Ignite
Issue Type
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/3572
IGNITE-7814 returned scala211.library.version parameter
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7814
Alt
Hi Folks,
Fixing the tests already brings some results. The number of falling tests
in a single run was reduced. Thanks to all, especially to Peter Ivanov,
Alexey Goncharuk, Pavel Kovalenko
There are 4 tickets that were not picked up by community (list at the end
of letter). Please look through a
Github user SomeFire closed the pull request at:
https://github.com/apache/ignite/pull/1876
---
Good question!
We've been waiting for a sign-off from Alexey Goncharuk and Sergey Kozlov
who are benchmarking and trying to address performance issues in
coopeartion.
Guys, please share your results and forecast.
--
Denis
On Sun, Feb 25, 2018 at 12:10 AM, Pavel Tupitsyn
wrote:
> Igniters,
>
>
Hi guys,
1. Alex, the point that Pavel tried to convey is that a user who will
get/put data using REST doesn't care if the data will be deserialized on
the server side. It just needs to work. So, the same user shouldn't know
about the keepBinary parameter, just turn it on for REST protocol by
defa
Hi Dmitriy,
Could you share some statistics? How many tests were fixed or merged in
one? Just curiuos.
--
Denis
On Mon, Feb 26, 2018 at 9:36 AM, Dmitry Pavlov
wrote:
> Hi Folks,
>
> Fixing the tests already brings some results. The number of falling tests
> in a single run was reduced. Thanks
> private int orgId;
> public int getOrganizationId() {...}
What an insane naming convention, who would do that? :)
Anyway, JSON field names should match binary metadata.
We have SQL via REST, so users would expect to use the same field names in
binary objects and SQL queries.
On Tue, Feb 27,
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3447
---
Turik, All,
Congratulations, the vote passed by lazy consensus. Feel free to merge the
pull-request into the main code base. Oleg, Yuri, should help with this.
Ping me once this happens, I would discuss documentation and promotion
related questions.
Please help to brag about this:
https://twitte
Igniters,
It's a pleasure for me to announce that ASF and Ignite community officially
accepted the genetic algorithms to Ignite machine learning code base:
http://incubator.apache.org/ip-clearance/ga-grid-ignite.html
Thanks to Turik Campbell for the contribution and Ignite ML contributors
and com
Valeri Chibaev created IGNITE-7815:
--
Summary: IgniteSpringBean implements SmartInitializingSingleton in
version 2.3.2+
Key: IGNITE-7815
URL: https://issues.apache.org/jira/browse/IGNITE-7815
Project:
Igniters,
To demonstrate Ignite SQL capabilities at different events, I usually:
1. take an SQL script
2. preload the data from the script with SQLLine tool that is already
shipped in Ignite
3. run DML operations from Web Console, code or other SQL tools
While SQLLine tool is availab
Nikolay Izhikov created IGNITE-7816:
---
Summary: DataFrame examples: wrong folder, hidden on TeamCity
Key: IGNITE-7816
URL: https://issues.apache.org/jira/browse/IGNITE-7816
Project: Ignite
I
Akshay Mhetre created IGNITE-7817:
-
Summary: Spark 'close' API call hangs when executed within ignite
service grid component
Key: IGNITE-7817
URL: https://issues.apache.org/jira/browse/IGNITE-7817
Pro
Aleksey Plekhanov created IGNITE-7818:
-
Summary: Incorrect assertion in PDS page eviction method
Key: IGNITE-7818
URL: https://issues.apache.org/jira/browse/IGNITE-7818
Project: Ignite
Is
43 matches
Mail list logo