Oleg Ignatenko created IGNITE-6872:
--
Summary: Linear regression should implement Model API
Key: IGNITE-6872
URL: https://issues.apache.org/jira/browse/IGNITE-6872
Project: Ignite
Issue Type:
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/3018
Ignite gg 12915
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12915
Alternatively you can review and app
GitHub user artemmalykh opened a pull request:
https://github.com/apache/ignite/pull/3017
Ignite-5218: Decision trees fixes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5218
Alternatively you ca
Dmitry,
Ignite is used by a variety of applications. Some models I saw were made
completely of stirngs. Others - of longs and decimals, etc.. It is
impossible to either prove or disprove what is the dominant data type. My
position is based on experience with Ignite users and approaches used in
oth
Hello, Igniters.
I've prepared PR [1] for this task [2],
upsource review [3] and tests results [4].
Could someone review it?
[1] https://github.com/apache/ignite/pull/3007
[2] https://issues.apache.org/jira/browse/IGNITE-6844
[3] https://reviews.ignite.apache.org/ignite/review/IGNT-CR-394
[4]
h
Hi Vladimir,
To my experience string is often used data type in business applications
and moreover, indexed.
> String type doesn't dominate in user models
what is the basis of this assumption?
Could you explain why String is more complex than byte[] compression. It
seems they both requires dictio
This would require shared dictionary, which is complex to maintain. We
evaluated this option, but rejected due to complexity. Another important
thing is that String type doesn't dominate in user models, so I do not see
why it should be a kind of special case.
пт, 10 нояб. 2017 г. в 18:45, Dmitry P
Aleksey Plekhanov created IGNITE-6871:
-
Summary: Implement new JMX metrics for partitions map monitoring
Key: IGNITE-6871
URL: https://issues.apache.org/jira/browse/IGNITE-6871
Project: Ignite
Aleksey Plekhanov created IGNITE-6870:
-
Summary: Implement new JMX metric for cache topology validation
monitoring
Key: IGNITE-6870
URL: https://issues.apache.org/jira/browse/IGNITE-6870
Project:
Aleksey Plekhanov created IGNITE-6868:
-
Summary: Implement new JMX metrics for TcpCommunicationSpi
monitoring
Key: IGNITE-6868
URL: https://issues.apache.org/jira/browse/IGNITE-6868
Project: Ignit
Aleksey Plekhanov created IGNITE-6869:
-
Summary: Implement new JMX metric for jobs monitoring
Key: IGNITE-6869
URL: https://issues.apache.org/jira/browse/IGNITE-6869
Project: Ignite
Issue
Vladimir,
orientation on string will also allow us to deduplicate strings in objects
during unmarshalling from page into heap.
Moreover, this can be first simple step of implementating more complex
algorithm.
Sincerely,
Dmitriy Pavlov
пт, 10 нояб. 2017 г. в 18:19, Vladimir Ozerov :
> Dmitry,
>
Aleksey Plekhanov created IGNITE-6867:
-
Summary: Implement new JMX metrics for topology monitoring
Key: IGNITE-6867
URL: https://issues.apache.org/jira/browse/IGNITE-6867
Project: Ignite
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/3016
Ignite 602
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-602
Alternatively you can review and apply these change
Dmitry,
What we've discussed so far in this topic is essentially the same concept.
We will deduplicate same byte sequences on page level.
On Fri, Nov 10, 2017 at 6:10 PM, Dmitry Pavlov
wrote:
> Hi Igniters,
>
> What do you think about implementing analogue of Java G1 collector featue
> 'String
Hi Igniters,
What do you think about implementing analogue of Java G1 collector featue
'String deduplication': -XX:+UseG1GC -XX:+UseStringDeduplication
Most of business application has almost all objects of type String. As
result char[] array is often on top of heap usage. To reduce consumption b
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2936
---
Alexander Belyak created IGNITE-6866:
Summary: Allocate offheap on client
Key: IGNITE-6866
URL: https://issues.apache.org/jira/browse/IGNITE-6866
Project: Ignite
Issue Type: Bug
Sec
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/3015
IGNITE-6836: Implemented query timeout.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6836
Alternatively you
Alin Andrei Corodescu created IGNITE-6865:
-
Summary: Wrong map query build using
Key: IGNITE-6865
URL: https://issues.apache.org/jira/browse/IGNITE-6865
Project: Ignite
Issue Type: Bu
Artem Malykh created IGNITE-6864:
Summary: Apply refactorings to decision trees code.
Key: IGNITE-6864
URL: https://issues.apache.org/jira/browse/IGNITE-6864
Project: Ignite
Issue Type: Task
Denis Mekhanikov created IGNITE-6863:
Summary: visorcmd: 'cache -a' shows nodes that are not matched by
nodeFilter
Key: IGNITE-6863
URL: https://issues.apache.org/jira/browse/IGNITE-6863
Project:
GitHub user dolphin1414 opened a pull request:
https://github.com/apache/ignite/pull/3014
IGNITE-6406: SQL: CREATE INDEX should fill index from multiple threads.
A parallel index creation and an SQL keyword PARALLEL parsing implemented.
You can merge this pull request into a Git rep
GitHub user gg-shq opened a pull request:
https://github.com/apache/ignite/pull/3013
IGNITE-6850 SQL: integrate index inline size to CREATE INDEX syntax
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite IGNI
Artem Malykh created IGNITE-6862:
Summary: SparseDistributedMatrixStorage cache config possibly
allows read of old state of matrix
Key: IGNITE-6862
URL: https://issues.apache.org/jira/browse/IGNITE-6862
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/3012
IGNITE-6861
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6861
Alternatively you can review and apply these
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/2940
---
Vladimir Ozerov created IGNITE-6861:
---
Summary: SQL parser: support CREATE TABLE and DROP TABLE commands
Key: IGNITE-6861
URL: https://issues.apache.org/jira/browse/IGNITE-6861
Project: Ignite
Turik,
1) Yes, it`s correct.
2.a) Model API is available, Trainer API in
PR(https://github.com/apache/ignite/pull/2936) which should be merged today
or tomorrow.
2.b) Yes, Trainer generates Model. Here is the Trainer interface:
public interface Trainer {
public M train(T data);
}
Regards,
Y
Alexandr Kuramshin created IGNITE-6860:
--
Summary: Lack of context information upon serializing and
marshalling (writeObject and writeFields)
Key: IGNITE-6860
URL: https://issues.apache.org/jira/browse/IGNITE-
Github user dspavlov closed the pull request at:
https://github.com/apache/ignite/pull/2967
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2995
---
Hi, Igniters!
I've prepared PR [1] for the issue IGNITE-1025 "Need to print out warning
if IP finder has a lot of addresses on Windows" [2] . TeamCity tests look
good [3]. Could someone review it?
Thanks in advance!
[1]https://github.com/apache/ignite/pull/2966
[2]https://issues.apache.org/jira/b
Ilya Borisov created IGNITE-6859:
Summary: Web console: does not work in IE11
Key: IGNITE-6859
URL: https://issues.apache.org/jira/browse/IGNITE-6859
Project: Ignite
Issue Type: Bug
Sec
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3011
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2990
---
36 matches
Mail list logo
