-
Notifications
You must be signed in to change notification settings - Fork 371
InexactError
in join
#1120
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
Comments
I guess the two columns have many unique values? Then that would be a duplicate of #985 (since the code is the same as for |
Yes, the columns have many unique values, so that is likely it. Thanks. |
Closing then. We really need somebody to investigate how we can avoid this failure. |
Hi! I found the same error: julia> const pdb_evalue = join(pdb_selected, selected, on = [:pfam, :seq])
ERROR: InexactError()
Stacktrace:
[1] convert(::Type{UInt32}, ::Int64) at ./int.jl:332
[2] PooledDataVecs(::DataFrames.DataFrame, ::DataFrames.DataFrame) at /home/diego/.julia/v0.6/DataFrames/src/abstractdataframe/join.jl:93
[3] #join#52(::Array{Symbol,1}, ::Symbol, ::Function, ::DataFrames.DataFrame, ::DataFrames.DataFrame) at /home/diego/.julia/v0.6/DataFrames/src/abstractdataframe/join.jl:202
[4] (::Base.#kw##join)(::Array{Any,1}, ::Base.#join, ::DataFrames.DataFrame, ::DataFrames.DataFrame) at ./<missing>:0 Is there a workaround to avoid it? Best regards,
|
Use DataFrames master... :-) |
Sadly,
|
I am experiencing an extremely difficult-to-reproduce
InexactError
when usingjoin
in master.The join is being done on two
DateTime
and oneInt64
columns. I attempted to reproduce the error by creating test dataframes with the same types and performing a similar join, but this does not seem to produce any error. The error also goes away if I join only on one of theDateTime
columns and theInt64
column. At the moment I'm not able to determine what is special about the dataframes that are causing the crash.Wish I could be more helpful, but I thought I'd post the issue in case it was obvious to someone what was going on.
The text was updated successfully, but these errors were encountered: