When querying data, the field name needs to be all uppercase

[gn01887818]

Use client mode.(java code)

CREATE TABLE `Sa` (
 `BuyID` bigint(20) unsigned NOT NULL DEFAULT 0,
 `Type` smallint(5) unsigned NOT NULL DEFAULT 0
);

Select BuyID from Sa;  =>No data found.
Select BUYID from Sa; => have information.

It feels like the field is capitalized.

Is there a way to change the settings of ignite DB?
Let select BuyID from Sa;
Can I query the information?

Thank you



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

The field name of the query result becomes uppercase

[gn01887818]

table schema:
CREATE TABLE `Wa` (
 `GameType` smallint(5) unsigned NOT NULL DEFAULT 0
);


ResultSet rs = conn.createStatement().executeQuery("select GameType from
Wa");

ResultSetMetaData resultSetMetaData = rs.getMetaData();

String name=getMetaData.getColumnLabel(1);

The name here is GAMETYPE, not GameType?

Because I need to take the name to do the processing, but found that the
name of the field defined by tale scheam is different.
Seems to be all uppercase

Do you have any additional settings to do?

Can make
String name=getMetaData.getColumnLabel(1);

name will be the GameType

Thank you



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite can not read the date type

[gn01887818]

Thank you.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite can not read the date type

[gn01887818]

Ignititedb defines a date type in a field.
JdbcResultSet uses the getBytes function (org.apache.ignite.internal.jdbc2)
Because the field will be java.sql.Date type, there will be an exception to
the last else.
How to deal with it?

 @Override public byte[] getBytes(int colIdx) throws SQLException {
Object val = getValue(colIdx);

if (val == null)
return null;

Class cls = val.getClass();

if (cls == byte[].class)
return (byte[])val;
else if (cls == Byte.class)
return new byte[] {(byte)val};
else if (cls == Short.class) {
short x = (short)val;

return new byte[] {(byte)(x >> 8), (byte)x};
}
else if (cls == Integer.class) {
int x = (int)val;

return new byte[] { (byte) (x >> 24), (byte) (x >> 16), (byte)
(x >> 8), (byte) x};
}
else if (cls == Long.class) {
long x = (long)val;

return new byte[] {(byte) (x >> 56), (byte) (x >> 48), (byte) (x
>> 40), (byte) (x >> 32),
(byte) (x >> 24), (byte) (x >> 16), (byte) (x >> 8), (byte)
x};
}
else if (cls == String.class)
return ((String)val).getBytes();
else
throw new SQLException("Cannot convert to byte[]: " + val,
SqlStateCode.CONVERSION_FAILED);
}


Can refer to line 462
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/jdbc2/JdbcResultSet.java



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cpu usage cannot be improved

[gn01887818]

I have confirmed that I am using jstack...
Jstack -J-d64 -m processId
I generated jstackInfo.txt like this.
Still have to make other orders?

That's right, currently using a regular hard drive, it seems to be stuck on
the hard drive speed.
Thank you



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cpu usage cannot be improved

[gn01887818]

I have confirmed that I am using jstack...
Jstack -J-d64 -m processId
I generated jstackInfo.txt like this.
Still have to make other orders?

That's right, currently using a regular hard drive, it seems to be stuck on
the hard drive speed.
Thank you



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cpu usage cannot be improved

[gn01887818]

I have confirmed that I am using jstack...
Jstack -J-d64 -m processId
I generated jstackInfo.txt like this.
Still have to make other orders?

That's right, currently using a regular hard drive, it seems to be stuck on
the hard drive speed.
Thank you



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cpu usage cannot be improved

[gn01887818]

Please look at the jstackInfo.txt file.
Inside is the information when ignite db is executed.
Thank you jstackInfo.txt
  



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cpu usage cannot be improved

[gn01887818]

How to dump, is there a file reference? Thank you



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cpu usage cannot be improved

[gn01887818]

1. Have tried stream mode
streamingFlushFrequency=500
streamingPerNodeBufferSize=512

2. Have tried System Pool, Queries Pool part,
The default is 24 (machine cpu core number), raised to 80

Still no way to improve the use of cpu.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cpu usage cannot be improved

[gn01887818]

Thank you. I will give it a try.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JDBC Client Node connection number problem

[gn01887818]

Thank you. I will give it a try.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Cpu usage cannot be improved

[gn01887818]

Use JDBC Client mode

There is an increase in the amount of writes, but the CPU utilization of the
machine where ignite DB is located has been maintained at 7%.
Want to ask what other settings can be opened, so that the cpu utilization
rate rises, improve the performance of writing?

Ps:
setDefaultDataRegionConfiguration has been set to 60gb



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JDBC Client Node connection number problem

[gn01887818]

Reason: Need to improve write DB performance.
The number of connections will affect the number of DBs written, so ask how
to increase the number of connections.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

JDBC Client Node connection number problem

[gn01887818]

If the JDBC Thin Driver requires 128 DB connections, there are actually 128
connections.

But if the JDBC Client Node Driver asks for 128 DB connections, it actually
creates up to seven connections.
(The number of connections is floating between 1 and 7)

Will the JDBC Client Node Driver,
Can I establish the corresponding number of connections according to the
number of connections I want?
Thank you



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

JDBC Client Node connection number problem

[gn01887818]

If the JDBC Thin Driver requires 128 DB connections, there are actually 128
connections.

But if the JDBC Client Node Driver asks for 128 DB connections, it actually
creates up to seven connections.
(The number of connections is floating between 1 and 7)

Will the JDBC Client Node Driver,
Can I establish the corresponding number of connections according to the
number of connections I want?
Thank you



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/