1. How can I explicitly load the Hive table into the IFGS don't using Java API? (I don't know Java) I use DUAL_SYNC. Here is my config. default-config.xml <http://apache-ignite-users.70518.x6.nabble.com/file/n12393/default-config.xml>
2. I attache sample data (test_ignite.rar). These are ORC files for Hive partitioned table. create table test_ignite (column1 double) partitioned by (calday string) stored as orc location '/path/test_ignite'; alter table test_ignite add partition (calday='2017-03-15'); alter table test_ignite add partition (calday='2017-03-16'); alter table test_ignite add partition (calday='2017-03-17'); alter table test_ignite add partition (calday='2017-03-18'); alter table test_ignite add partition (calday='2017-03-19'); alter table test_ignite add partition (calday='2017-03-20'); select calday, count(*) from test_ignite where calday between '2017-03-15' and '2017-03-20' group by calday order by calday; Correct result on one ignite node: +-------------+-----------+--+ | calday | _c1 | +-------------+-----------+--+ | 2017-03-15 | 36564815 | | 2017-03-16 | 36872463 | | 2017-03-17 | 36900812 | | 2017-03-18 | 36904198 | | 2017-03-19 | 36999930 | | 2017-03-20 | 37029921 | +-------------+-----------+--+ 6 rows selected (49.88 seconds) Wrong result on two ignite nodes: +-------------+-----------+--+ | calday | _c1 | +-------------+-----------+--+ | 2017-03-16 | 24582164 | | 2017-03-17 | 12301380 | | 2017-03-18 | 36904198 | | 2017-03-19 | 12332322 | +-------------+-----------+--+ 4 rows selected (45.199 seconds) test_ignite.rar <http://apache-ignite-users.70518.x6.nabble.com/file/n12393/test_ignite.rar> 3. I started ignite nodes sequentially on 6 servers (dn1, dn2, dn3, dn4, dn5, dn6). They formed 3 clusters: dn1-dn3-dn6 dn2-dn4 dn5 ignite-node-dn1.log <http://apache-ignite-users.70518.x6.nabble.com/file/n12393/ignite-node-dn1.log> ignite-node-dn2.log <http://apache-ignite-users.70518.x6.nabble.com/file/n12393/ignite-node-dn2.log> ignite-node-dn3.log <http://apache-ignite-users.70518.x6.nabble.com/file/n12393/ignite-node-dn3.log> ignite-node-dn4.log <http://apache-ignite-users.70518.x6.nabble.com/file/n12393/ignite-node-dn4.log> ignite-node-dn5.log <http://apache-ignite-users.70518.x6.nabble.com/file/n12393/ignite-node-dn5.log> ignite-node-dn6.log <http://apache-ignite-users.70518.x6.nabble.com/file/n12393/ignite-node-dn6.log> 4. As regard Evgeniy's comment it sounds reasonable, but I'm trying to cache some hot Hive tables so that different users run their queries faster because they don't need to read the same data from the disk. Still hope this is possible) -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/HDP-Hive-Ignite-tp12195p12393.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
