Grant Haywood created IGNITE-9343:
-
Summary: ignite-geospatial is not on maven central
Key: IGNITE-9343
URL: https://issues.apache.org/jira/browse/IGNITE-9343
Project: Ignite
Issue Type: Bug
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New test failure in master SchemaExchangeSelfTest.testNonEmptyDynamic
I've removed the ARRAY data type from the supported list.
Regardless of this, Vova, could you answer to Dmiry's question?
--
Denis
On Tue, Aug 14, 2018 at 8:28 AM Dmitriy Setrakyan
wrote:
>
>
> On Tue, Aug 14, 2018 at 3:34 AM, Vladimir Ozerov
> wrote:
>
>> Hi,
>>
>> No, we do not support
Hi,
Please tell your JIRA id so that we grant required permissions.
--
Denis
On Tue, Aug 21, 2018 at 7:59 PM SUMIT KESARWANI
wrote:
> Hi All,
> wanted to contribute in apache ignite project.
> i request to admin , please provide me the access for jira to assign issue
> for myself.
>
>
>
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New test failure in master
IgniteCacheAtomicProtocolTest.testPutReaderUpdate1
Hi All,
wanted to contribute in apache ignite project.
i request to admin , please provide me the access for jira to assign issue
for myself.
-Sumit Kesarwani
India
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New test failure in master
IgniteClusterActivateDeactivateTestWithPersistence.testClientReconnectClusterActivated
Stuart,
Thanks for pointing this out, I was not aware that we use Spark database
concept this way. Actually, this confuses me a lot. As far as I understand,
catalog is created in the scope of a particular IgniteSparkSession, which
in turn is assigned to a particular IgniteContext and therefore
Dmitriy, yes, you correctly understood my idea.
вт, 21 авг. 2018 г. в 22:03, Vladimir Ozerov :
> Guys,
>
> Do we have any numbers for real workloads? Or at least Yardstick.
>
> вт, 21 авг. 2018 г. в 21:04, Dmitriy Pavlov :
>
> > Let us double-check current options. Maybe I'm mistaken about Alex
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/4590
Ignite 2.4.9
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.9
Alternatively you can review and apply
Thanks, Nikolay!
I think it is important to include the links to all important Jira tickets
in this thread, so that the community can track them.
D.
On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov
wrote:
> Hello, Dmitriy.
>
> I think Transparent Data Encryption will be available in 2.7
>
>
Guys,
Do we have any numbers for real workloads? Or at least Yardstick.
вт, 21 авг. 2018 г. в 21:04, Dmitriy Pavlov :
> Let us double-check current options. Maybe I'm mistaken about Alex
> Plehanov's idea.
>
> Let's introduce the following variables and functions:
> data - our block.
>
Let us double-check current options. Maybe I'm mistaken about Alex
Plehanov's idea.
Let's introduce the following variables and functions:
data - our block.
OldImpl(data) = X
NewImpl(data) = Y
NewImpl(data) ^ C = Y ^ C, where C is constant, ^ is bitwise XOR operation.
And NewImpl(data) ^ C = X =
Hi Dmitriy,
The Bot is able to detect a frequent change of test status, but currently
only 50 last runs count. Same is true for the failure rate.
This value can be easily changed to 70 or 100, moreover, the auto
trigger feature gives us much more builds.
We can improve these rules. We can add
Hello,
Clearly Storage Class Memory represents a breakthrough for "in memory" grids
and some people already tried it on Ignite :
http://dmagda.blogspot.com/2017/10/3d-xpoint-outperforms-ssds-verified-on.ht
ml
I would like to know what is the position of the community towards the
Persistent
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/4589
Replace TcpDiscoveryMulticastIpFinder with TcpDiscoveryVmIpFinder in tests
Created for testing
You can merge this pull request into a Git repository by running:
$ git pull
I think plugin will be more pretty looking, but comments can contain any
information, so they can be more usefull. I agree with your idea to create
bot instead of plugin.
As for fail rate - I'm not sure it is working as you describe.
I'm looking on my runAll [1]. There is
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/4588
IGNITE-9326 Fixed node failure processor invocation when EntryProcessâ¦
â¦or result serialization throws an exception
You can merge this pull request into a Git repository by running:
$
Nikolay, Val,
The JDBC Spark datasource[1] -- as far as I can tell -- has no
ExternalCatalog implementation, it just uses the database specified in the
JDBC URL. So I don't believe there is any way to call listTables() or
listDatabases() for JDBC provider.
The Hive ExternalCatalog[2] makes the
Hi Dmitrii,
I'm not sure we're able to install Github apps to Apache mirrors.
The simplest solution, what can be as efficient as a plugin, is fake MTCGA
bot account in Github, which will provide PR comments using Github program
interface. What do you think?
A new test failure can be identified
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4581
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4585
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4582
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4440
---
Hello, Igniters!
I want to suggest improvement for TeamCity Helper [1] – we need an easy way
to get list of failed tests that don’t fall in the master branch. These
tests should:
* fail in the PR
* not fail in the master
* not be flaky.
Also, I want to suggest to create a GitHub plugin, which
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4587
IGNITE-9270 Thread-per-partition during Tx commit
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9270
Igor Sapego created IGNITE-9342:
---
Summary: The same SQL request with multiple statements produces
different result
Key: IGNITE-9342
URL: https://issues.apache.org/jira/browse/IGNITE-9342
Project:
Alex
In that case the data becomes in unpredictable state (mix of new and old
methods) and there's a chance that some partitions will be never touched
and never converted. It will force us always support old compression.
I suppose the explicit conversion that clearly say what is happening now
and
Ivan Rakov created IGNITE-9341:
--
Summary: Notify metastorage listeners righ before start of
discovery processor
Key: IGNITE-9341
URL: https://issues.apache.org/jira/browse/IGNITE-9341
Project: Ignite
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/4586
IGNITE-9279
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9279-1
Alternatively you can review and apply
Hi Alex,
I agree that we can't move all metrics to ignite.metrics() and SPI metrics
is a good example here. I propose to move at least dataRegionMetrics,
dataStorageMetrics to it, since the main API class is not a good place for
such things. If we will decide to choose option 1 from my first
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/4585
IGNITE-9336: Remove random test dataset generation
1. Remove ThreadLocalRandom usages in test dataset data generation
2. Refactor Trainer tests
3. Propose a few static datasets generated
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4138
---
Hello, Igniters.
I assigned ticket [1] created by Denis and want to clarify how to log
committed size.
The metric offHeapSize (in DataRegionMetricsImpl) is always
calculated, but getOffHeapSize returns zero if memory metrics are
disabled for this data region.
So I see the following options:
1.
Sergey, converting data also force us to introduce some flag to WAL
segments/records or convert WAL segments too. WAL segments can be archived,
they also can be compressed.
IMO we better should not introduce any compatibility modes, left data as is
and always just convert crc value returned by
Ilya Borisov created IGNITE-9339:
Summary: Web console: form-field-size improvements
Key: IGNITE-9339
URL: https://issues.apache.org/jira/browse/IGNITE-9339
Project: Ignite
Issue Type:
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/4584
IGNITE-2.4.8.b5
Created for testing.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.8.b5
Alternatively
Hello, Stuart.
Can you do some research and find out how schema is handled in Data Frames for
a regular RDBMS such as Oracle, MySQL, etc?
В Пн, 20/08/2018 в 15:37 -0700, Valentin Kulichenko пишет:
> Stuart, Nikolay,
>
> I see that the 'Table' class (returned by listTables method) has a
Stepan Pilschikov created IGNITE-9338:
-
Summary: ML TF integration: tf cluster can't connect after killing
first node with default port 10800
Key: IGNITE-9338
URL:
Roman,
I worked recently on rebalance improvements and haven't found any problems
with delayed cache rebalacne.
Agree with you - let's uncomment this and remove scary comment. Will you
create a ticket for it?
In case of any problems we can easily detec deadlock with newly configured
Alexey Kuznetsov created IGNITE-9337:
Summary: VisorNodeDataCollectorTask may produce HUGE result in
case of large cluster with many caches
Key: IGNITE-9337
URL:
Aleksey Zinoviev created IGNITE-9336:
Summary: [ML] ANN/SVM Trainer tests produce unpredictable results
due to random data generation
Key: IGNITE-9336
URL: https://issues.apache.org/jira/browse/IGNITE-9336
Hello, Dmitriy.
I think Transparent Data Encryption will be available in 2.7
В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> Hi Nikolay,
>
> Thanks for being the release manager!
>
> I am getting a bit lost in all these tickets. Can we specify some
> high-level tickets, that are not
43 matches
Mail list logo
