Open GoogleCodeExporter opened 8 years ago
Need to support dates to the extent that we can parse date formats in web logs
etc.
Original comment by vinay...@gmail.com
on 6 Apr 2012 at 8:55
Jarod, did you fix this in your recent temporal type changes which are now into
asterix_stabilization ? can you pls confirm, thanks.
Original comment by khfaraaz82
on 19 Nov 2012 at 3:57
We have implemented the import feature from adm file, however it has not been
tested on delimited text. I will verify this in my temporal_functionality
branch and fix there if not yet.
Original comment by jarod...@gmail.com
on 19 Nov 2012 at 4:29
Reassign to me to fix it.
Original comment by jarod...@gmail.com
on 19 Nov 2012 at 4:30
Thanks Jarod.
Original comment by khfaraaz82
on 19 Nov 2012 at 7:14
Confirmed as missing features. Will be fixed in the temporal functionality
branch.
Original comment by jarod...@gmail.com
on 20 Nov 2012 at 4:54
Seems that this involves changes to hyracks, as the value parsers used in
NtDelimitedDataTupleParserFactory are directly from Hyracks package. However as
far as I know other importing parsers, like the one for importing json files,
are in asterix. I think these two cases should be consistant. I need more
investigation on this.
Original comment by jarod...@gmail.com
on 20 Nov 2012 at 5:07
This issue was closed by revision r942.
Original comment by jarod...@gmail.com
on 25 Nov 2012 at 7:41
Original comment by jarod...@gmail.com
on 25 Nov 2012 at 11:12
Why is this FixedInBranch ?
Is it blocked on something that is stopping it from making it to
asterix_stabilization ?
If the fix is waiting on a code review, it should not be marked as
FixedInBranch.
Please update the current status of this issue with comments. Thanks.
Original comment by khfaraaz82
on 19 Jan 2013 at 12:57
The fix is in the asterix_stabilization_temporal_functionality branch. The code
need to be reviewed before being merged back.
Original comment by jarod...@gmail.com
on 24 Jan 2013 at 5:37
The overall external temporal data importing (including interval, date, time,
datetime and duration) will be finished after the new lexer is merged.
Original comment by jarod...@gmail.com
on 11 Feb 2013 at 4:29
Do we still need to support non-primitive types (types except for the int,
string, double; saying temporal types)? As from Diego's work we now have good
support for adm (json) data source, delimited external data may be converted
into the adm before importing?
Original comment by jarod...@gmail.com
on 4 Mar 2013 at 11:27
We need to support temporal types for sure. Ji Mahn's work needs it, and
Eugenia's work can also benefit from it. I remember once Jarod, Diego, and I
had a discussion about how to deal with complicated strings in lexer, and
decided to let the parser interprete the strings. Is that conclusion related?
Original comment by che...@gmail.com
on 5 Mar 2013 at 6:08
Documentation to be added to the docs section that talks about loading data
Original comment by vinay...@gmail.com
on 17 May 2013 at 7:45
Original issue reported on code.google.com by
khfaraaz82
on 14 Mar 2012 at 5:17