[jira] [Commented] (PHOENIX-4193) Pherf - llegalArgumentException while DataTypeMapping some standard field e.g. SMALLINIT, TINYINT, BOOLEAN
[ https://issues.apache.org/jira/browse/PHOENIX-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16162236#comment-16162236 ] Mujtaba Chohan commented on PHOENIX-4193: - [~rgore] You need to use supported datatypes for now. Meanwhile as I add support for the datatypes you need, as a workaround you can use similar datatypes. Ex. {{INT}} in place of {{TIMYINT}} > Pherf - llegalArgumentException while DataTypeMapping some standard field > e.g. SMALLINIT, TINYINT, BOOLEAN > -- > > Key: PHOENIX-4193 > URL: https://issues.apache.org/jira/browse/PHOENIX-4193 > Project: Phoenix > Issue Type: Bug >Reporter: Ravindra Gore > > Currently only standard types are supported in Pherf scenarios generation. > To generate the scenarios for tables with non-supported data types, we try > mapping them to supported type. > e.g. INTEGER to TINYINT mapping > > INTEGER > RANDOM > 2 > 0 > 10 > APP_ID > > Though generation of the test data fails with the gack: > java.lang.IllegalArgumentException: No enum constant > org.apache.phoenix.pherf.configuration.DataTypeMapping.TINYINT > java.lang.IllegalArgumentException: No enum constant > org.apache.phoenix.pherf.configuration.DataTypeMapping.TINYINT > at java.lang.Enum.valueOf(Enum.java:238) > at > org.apache.phoenix.pherf.configuration.DataTypeMapping.valueOf(DataTypeMapping.java:23) > at > org.apache.phoenix.pherf.util.PhoenixUtil.getColumnsFromPhoenix(PhoenixUtil.java:248) > at > org.apache.phoenix.pherf.workload.WriteWorkload.getBatches(WriteWorkload.java:208) > at > org.apache.phoenix.pherf.workload.WriteWorkload.exec(WriteWorkload.java:182) > at > org.apache.phoenix.pherf.workload.WriteWorkload.access$100(WriteWorkload.java:56) > at > org.apache.phoenix.pherf.workload.WriteWorkload$1.run(WriteWorkload.java:159) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Same issue is observerd for BOOLEAN and SMALLINT. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PHOENIX-4193) Pherf - llegalArgumentException while DataTypeMapping some standard field e.g. SMALLINIT, TINYINT, BOOLEAN
[ https://issues.apache.org/jira/browse/PHOENIX-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161868#comment-16161868 ] Ravindra Gore commented on PHOENIX-4193: [~mujtabachohan] FYI. Are there any standard workarounds for all these data types? > Pherf - llegalArgumentException while DataTypeMapping some standard field > e.g. SMALLINIT, TINYINT, BOOLEAN > -- > > Key: PHOENIX-4193 > URL: https://issues.apache.org/jira/browse/PHOENIX-4193 > Project: Phoenix > Issue Type: Bug >Reporter: Ravindra Gore > > Currently only standard types are supported in Pherf scenarios generation. > To generate the scenarios for tables with non-supported data types, we try > mapping them to supported type. > e.g. INTEGER to TINYINT mapping > > INTEGER > RANDOM > 2 > 0 > 10 > APP_ID > > Though generation of the test data fails with the gack: > java.lang.IllegalArgumentException: No enum constant > org.apache.phoenix.pherf.configuration.DataTypeMapping.TINYINT > java.lang.IllegalArgumentException: No enum constant > org.apache.phoenix.pherf.configuration.DataTypeMapping.TINYINT > at java.lang.Enum.valueOf(Enum.java:238) > at > org.apache.phoenix.pherf.configuration.DataTypeMapping.valueOf(DataTypeMapping.java:23) > at > org.apache.phoenix.pherf.util.PhoenixUtil.getColumnsFromPhoenix(PhoenixUtil.java:248) > at > org.apache.phoenix.pherf.workload.WriteWorkload.getBatches(WriteWorkload.java:208) > at > org.apache.phoenix.pherf.workload.WriteWorkload.exec(WriteWorkload.java:182) > at > org.apache.phoenix.pherf.workload.WriteWorkload.access$100(WriteWorkload.java:56) > at > org.apache.phoenix.pherf.workload.WriteWorkload$1.run(WriteWorkload.java:159) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Same issue is observerd for BOOLEAN and SMALLINT. -- This message was sent by Atlassian JIRA (v6.4.14#64029)