Re: yet another question...perhaps dumb...JOIN with two conditions

2015-09-11 Thread M. Aaron Bossert
AH! Now I get it...I am running on a pretty beefy cluster...I would have thought this would work, even if a bit slower. Do you know which timeout settings I would need to alter to get this to work? On Fri, Sep 11, 2015 at 12:26 PM, Maryann Xue wrote: > Yes, I know. That

Re: yet another question...perhaps dumb...JOIN with two conditions

2015-09-11 Thread James Heather
With your query as it stands, you're trying to construct 250K*270M pairs before filtering them. That's 67.5 trillion. You will need a quantum computer. I think you will be better off restructuring... James On 11 Sep 2015 5:34 pm, "M. Aaron Bossert" wrote: > AH! Now I get

Re: yet another question...perhaps dumb...JOIN with two conditions

2015-09-11 Thread Aaron Bossert
Don't have a quantum computer...but am on a small supercomputer ;). 1500 cores, 6TB of memory, 40TB of SSD, and a few hundred TB of spinning disks... Sent from my iPhone > On Sep 11, 2015, at 1:23 PM, James Heather wrote: > > With your query as it stands, you're

Re: yet another question...perhaps dumb...JOIN with two conditions

2015-09-11 Thread Maryann Xue
Hi Aaron, As Jaime pointed out, it is a non-equi join. And unfortunately it is handled as CROSS join in Phoenix and thus is not very efficient. For each row from the left side, it will be joined with all of the rows from the right side before the condition is a applied to filter the joined

Re: yet another question...perhaps dumb...JOIN with two conditions

2015-09-10 Thread Jaime Solano
Hi Aaron, The JOIN you're trying to run is a non-equi join, meaning that the ON condition is not an equality ('>=' and '<=' in your case). This type of join is not supported in Phoenix versions prior to 4.3 In Phoenix 4.3+, you can do something like this: SELECT * FROM NG.AKAMAI_FORCEFIELD AS

yet another question...perhaps dumb...JOIN with two conditions

2015-09-10 Thread M. Aaron Bossert
I am trying to execute the following query, but get an error...is there another way to achieve the same result by restructuring the query? QUERY: SELECT * FROM NG.AKAMAI_FORCEFIELD AS FORC INNER JOIN NG.IPV4RANGES AS IPV4 ON FORC.SOURCE_IP >= IPV4.IPSTART AND FORC.SOURCE_IP <= IPV4.IPEND;