Yes I am just trying to bulk load from an ADM file that's the result of querying. It's annoying to have to mangle it with sed or similar, as its about 4GB. On Aug 19, 2015 2:41 AM, "Chris Hillery" <[email protected]> wrote:
> I noticed that the output wasn't re-parseable as input last week when > coming up with the proposed JSON serialization. In particular, the numeric > suffixes like 0.0d, 15i8, 333333i32, and so on didn't parse as AQL > (although interestingly 32.5f does). I wasn't aware that it used to work, > though. It's an odd disconnect between ADM and AQL, at the least. It sounds > like you're seeing the same issue when parsing as actual ADM? > > Ceej > aka Chris Hillery > > On Wed, Aug 19, 2015 at 1:43 AM, Ian Maxon <[email protected]> wrote: > > > Hi, > > Has ADM output from Asterix stopped being round-trippable? I'm trying to > > load a record I got from dumping from another instance, via the REST API, > > requesting 'application-x-adm' in the accept header. First I had to > remove > > the outer wrapper list that was added a while back, which I suppose isn't > > awful, but now it seems like I'm getting more subtle errors. For example, > > trying to load a record, and the parse fails once it sees a field like > this > > in a record : > > > > { ... , "Rank": 0.0d, .... } > > > > With: > > > > Parse error at (1, 4421) expecting: <DOUBLE_CONS> <DATE_CONS> > > <DATETIME_CONS> <DURATION_CONS> <DAY_TIME_DURATION_CONS> > > [AdmLexerException] > > > > Any ideas? > > > > > > Thanks, > > - Ian > > >
