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

Error: Table 'aggregation_tmp_....' already exists #18

Open
kristinriebe opened this issue Oct 18, 2013 · 1 comment
Open

Error: Table 'aggregation_tmp_....' already exists #18

kristinriebe opened this issue Oct 18, 2013 · 1 comment

Comments

@kristinriebe
Copy link

A query like this:

SELECT fp.particleId
FROM
MDR1.FOFParticles AS fp
WHERE fp.fofId = 85000000000
LIMIT 10-- The query plan used to run this query: -------------------------------------------------- CALL paquExec('SELECT fp.particleId AS fp.particleId FROM MDR1.FOFParticles AS fp WHERE ( fp.fofId = 85000000000 ) LIMIT 0,10', 'aggregation_tmp_86794282')-- USE spider_tmp_shard-- SET @i=0-- CREATE TABLE multidark_user_kristin.test-simple ENGINE=MyISAM SELECT @i:=@i+1 AS row_id, distinct_res_table.* FROM ( SELECT DISTINCT fp.particleId
FROM aggregation_tmp_86794282 LIMIT 0,10 ) as distinct_res_table-- CALL paquDropTmp('aggregation_tmp_86794282')

gives the error:
Table 'aggregation_tmp_86794282' already exists

I can't spot a mistake in the query plan, however.

@adrpar
Copy link
Owner

adrpar commented Oct 18, 2013

retrieve IP lists properly from spider tables - problem is, that if multiple tables point to different nodes, all nodes are asked to send results. if IPs are different, but nodes identical, the problem above arises

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

No branches or pull requests

2 participants