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.

Sign up for GitHub

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

Jump to bottom

toDate() no longer works properly in the development version #1405

Closed
ettorerizza opened this issue Dec 27, 2017 · 3 comments
Closed

toDate() no longer works properly in the development version #1405

ettorerizza opened this issue Dec 27, 2017 · 3 comments
Assignees
@jackyq2015
Labels
java version compatibility Making sure OpenRefine runs on as many Java versions as possible Priority: Critical Highlights issues that demand immediate action. Type: Bug Issues related to software defects or unexpected behavior, which require resolution.
Milestone
3.0

Comments

@ettorerizza
Copy link
Member

By trying the function toDate() on string-dates like "28/09/2015" or "12 may 2017", everything looks fine in the transformation window, but the result displayed is this:

java.util.GregorianCalendar[time=?,areFieldsSet=false,areAllFieldsSet=false,lenient=true,zone=sun.util.calendar.ZoneInfo[id="Europe/Paris",offset=3600000,dstSavings=3600000,useDaylight=true,transitions=184,lastRule=java.util.SimpleTimeZone[id=Europe/Paris,offset=3600000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=2,startMonth=2,startDay=-1,startDayOfWeek=1,startTime=3600000,startTimeMode=2,endMode=2,endMonth=9,endDay=-1,endDayOfWeek=1,endTime=3600000,endTimeMode=2]],firstDayOfWeek=2,minimalDaysInFirstWeek=4,ERA=?,YEAR=2014,MONTH=7,WEEK_OF_YEAR=?,WEEK_OF_MONTH=?,DAY_OF_MONTH=28,DAY_OF_YEAR=?,DAY_OF_WEEK=?,DAY_OF_WEEK_IN_MONTH=?,AM_PM=?,HOUR=?,HOUR_OF_DAY=?,MINUTE=?,SECOND=?,MILLISECOND=?,ZONE_OFFSET=?,DST_OFFSET=?]
--
@jackyq2015 jackyq2015 added Type: Bug Issues related to software defects or unexpected behavior, which require resolution. java version compatibility Making sure OpenRefine runs on as many Java versions as possible labels Dec 28, 2017
@wetneb
Copy link
Sponsor Member

wetneb commented Dec 28, 2017

This is probably linked to the failing test case in #1300.

@wetneb wetneb added the Priority: High Denotes issues that require urgent attention and may be blocking progress. label Feb 2, 2018
@thadguidry thadguidry added Priority: Critical Highlights issues that demand immediate action. and removed Priority: High Denotes issues that require urgent attention and may be blocking progress. labels Mar 13, 2018
@thadguidry thadguidry added this to the 3.0 milestone Mar 13, 2018
@thadguidry
Copy link
Member

@wetneb Can you work on this over the next 2 weeks ? (invoice-able work)

@wetneb
Copy link
Sponsor Member

wetneb commented Apr 19, 2018

@thadguidry, sure, but let's first get #1564 fixed, maybe? As there is some overlap.

@jackyq2015 jackyq2015 self-assigned this Apr 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jackyq2015 jackyq2015

Labels
java version compatibility Making sure OpenRefine runs on as many Java versions as possible Priority: Critical Highlights issues that demand immediate action. Type: Bug Issues related to software defects or unexpected behavior, which require resolution.
Projects
None yet
Milestone
3.0
Development

No branches or pull requests
4 participants
@wetneb @thadguidry @ettorerizza @jackyq2015