Get ExecutorService from SiddhiAppcontext instead of ScheduledExecutorService.
Approach
Earlier siddhi-io-kafka source used ScheduledExecutorService from SiddhiAppContext to handle partition wise threads and that SheduledExecuterService has only 5 threadpools. So Kafka source can't handle more than 5 partition even though the user provides more than 5 partitions from the partition.no.list parameter. In order to solve this, ExecutoreService is used instead of SheduleExecutorService from the SiddhiAppContext
Purpose
Resolve #80
Goals
Get ExecutorService from SiddhiAppcontext instead of ScheduledExecutorService.
Approach
Earlier siddhi-io-kafka source used ScheduledExecutorService from SiddhiAppContext to handle partition wise threads and that SheduledExecuterService has only 5 threadpools. So Kafka source can't handle more than 5 partition even though the user provides more than 5 partitions from the
partition.no.list
parameter. In order to solve this, ExecutoreService is used instead of SheduleExecutorService from the SiddhiAppContextSecurity checks