Oleg,
Looks good to me. Please consider the notes left in the ticket. I want us to
prepare a script for Windows, review the language for help notice and errors,
put together documentation. Prachi will be able to help with the editing and
documentation.
—
Denis
> On Oct 9, 2017, at 10:13 AM,
Hi Yuri,
Sounds impressive!
The only suggestion I have for you guys is to copy the dev list more for ML
related discussions. This will let the community to keep track of your
activities on a daily basis and do proposal to algorithms you’ve been working
on.
Agreed?
—
Denis
> On Oct 10,
Hi Igniters!
I want to provide some updates about current state of ml module, so let me
introduce that we already have:
* OLS lin regression(not so efficient in distributed case, but Alexey
Zinoviev already working to fix that, IGNITE-6222).
* K-means (IGNITE-5113).
* Decision tree(almost done
Igor Sapego created IGNITE-6594:
---
Summary: Add lazy flag to the list of the ODBC connection string
attributes.
Key: IGNITE-6594
URL: https://issues.apache.org/jira/browse/IGNITE-6594
Project: Ignite
Igor Sapego created IGNITE-6593:
---
Summary: Document C and SQL types, supported by ODBC driver.
Key: IGNITE-6593
URL: https://issues.apache.org/jira/browse/IGNITE-6593
Project: Ignite
Issue
Igor Sapego created IGNITE-6592:
---
Summary: Describe Ignite C++ pointer reading and writing semantics
Key: IGNITE-6592
URL: https://issues.apache.org/jira/browse/IGNITE-6592
Project: Ignite
Github user alamar closed the pull request at:
https://github.com/apache/ignite/pull/2460
---
Github user alamar closed the pull request at:
https://github.com/apache/ignite/pull/2484
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2825
---
Evgenii Zhuravlev created IGNITE-6591:
-
Summary: JdbcThinErrorsSelfTest.testBatchUpdateException() should
be removed, as batch updates already supported
Key: IGNITE-6591
URL:
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/2826
IGNITE-6140 JDBC thin: implement DataSource interface
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Ilya Kasnacheev created IGNITE-6590:
---
Summary: TCP port in bin/control.sh differs from default
Key: IGNITE-6590
URL: https://issues.apache.org/jira/browse/IGNITE-6590
Project: Ignite
Issue
Vladislav Pyatkov created IGNITE-6589:
-
Summary: Encountered incompatible class loaders for cache
Key: IGNITE-6589
URL: https://issues.apache.org/jira/browse/IGNITE-6589
Project: Ignite
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/2825
IGNITE-6588
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6588
Alternatively you can review and apply these
Vladimir Ozerov created IGNITE-6588:
---
Summary: SQL: optimize segment resolution in GridH2IndexBase when
index is not segmented
Key: IGNITE-6588
URL: https://issues.apache.org/jira/browse/IGNITE-6588
Alexey Goncharuk created IGNITE-6587:
Summary: Ignite watchdog service
Key: IGNITE-6587
URL: https://issues.apache.org/jira/browse/IGNITE-6587
Project: Ignite
Issue Type: Improvement
Val, I really like your idea to implement common mechanism for all APIs.
Can you please file a ticket?
--Yakov
Dmitriy,
Yes, I still see this mirror in "Selected mirror:" box and it's usually
default for me. However it looks that it is up today and I'm able to
download Ignite from it.
I wonder what's long term status of this mirror though.
Regards,
--
Ilya Kasnacheev
2017-10-09 21:08 GMT+03:00
GitHub user ntikhonov opened a pull request:
https://github.com/apache/ignite/pull/2824
Ignite 1.9.7 b1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.9.7-b1
Alternatively you can review and
Denis Koblov created IGNITE-6586:
Summary: Spring bean as ignite service
Key: IGNITE-6586
URL: https://issues.apache.org/jira/browse/IGNITE-6586
Project: Ignite
Issue Type: Wish
Github user ybabak closed the pull request at:
https://github.com/apache/ignite/pull/2501
---
Denis,
There is an overhead for each separate fsync syscall which may become
significant with a large number of files, so having fewer files will
perform better in general. As for the heap structures overhead, this is
true that on large topologies having several cache groups will
significantly
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2815
---
23 matches
Mail list logo
