Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CARBONDATA-264]Fixed limit query scan time statistics issue #184

Closed
wants to merge 1 commit into from

Conversation

kumarvishal09
Copy link
Contributor

Problem: Scan time is not logging in statistics in case of limit query
Soluntion: Moved statistics recording from iterator to queryExecutor finish method as in case of limit query after consuming records call is not coming to hasNext method

@kumarvishal09
Copy link
Contributor Author

@@ -36,6 +36,7 @@
@Override public CarbonIterator<Object[]> execute(QueryModel queryModel)
throws QueryExecutionException {
List<BlockExecutionInfo> blockExecutionInfoList = getBlockExecutionInfos(queryModel);
queryProperties.scanStartTime=System.currentTimeMillis();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

incorrect code style

@@ -91,5 +89,10 @@
* list of blocks in which query will be executed
*/
protected List<AbstractIndex> dataBlocks;
/**
* start time scanning
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is the start time of scanning?

@ravipesala
Copy link
Contributor

Build Failed, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder/

Beyyes pushed a commit to Beyyes/carbondata that referenced this pull request Jul 12, 2018
* fix bug

* fix nodeGpuType empty string

* fix user specified GPU atrribute not compatible with GPU type

* fix bug
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants