none
Datatype differs to index profile after indexing RRS feed

  • Question

  • We're currently running FAST ESP V5.3.0 build_08070800 on SunOS. Fields and datatypes are defined in index profile. After indexing datatypes of multiple fields are string instead of date (as opposed to index profile).

    Index is feeded by a view from an oracle database. Fields delivered to FAST are datatypes DATE in oracle converted to varchar by TO_CHAR(date, 'YYYY-MM-DD'). On our test-platform this all worked as intended. Fields in index are listed as datatype DATE. After indexing on our live-platform fields are listed as STRING.

    What we tried so far:

    *) New feeding of whole collection with either date or varchar delivered from oracle view: Fields in index always listed as STRING.

    *) Feeding a document from test-database to live-platform: Fields still listed as STRING.

    *) Comparing all stages in pipeline of live-platform to test-platform: All stages are identical and in the same order.

    *) LOCAL-Settings of live-OS are identical to test-OS.

    *) Field in index is displayed as, eg., 2011-03-01T00:00:00Z (but is STRING datatype) .

    So the question is: Does anyone have an idea what causes this problem or can give an example what else to try?

    Tuesday, September 30, 2014 7:17 AM

All replies

  • The field displayed in question here is a datetime and NOT a string.
    For example from my OOB, I can see the definition of processingtime in the index profile as :
     <field name="processingtime" type="datetime" fullsort="yes"/>

    From search results:
    <FIELD NAME="processingtime">2014-06-23T14:32:31Z</FIELD>

    Fixml converted to epoch time ans summary fields:
    <context name="bconprocessingtime"><![CDATA[3696784712]]></context>
     <sField name="bsumprocessingtime"><![CDATA[2014-06-23T14:32:31Z]]></sField>

    How are you determining that the field is string?

    In ESP supported date formats are:
    YYYY-MM-DD
    YYYY-MM-DDThh:mm:ss
    YYYY-MM-DDThh:mm:ssZ

    Tuesday, September 30, 2014 8:40 PM
  • The field displayed in question here is a datetime and NOT a string.
    For example from my OOB, I can see the definition of processingtime in the index profile as :
     <field name="processingtime" type="datetime" fullsort="yes"/>

    Hi Patrick,

    thanks for the help! The field may be displayed as datetime but the datatype is still string. Our definition in index profile looks similar as yours:

    <field name="commentdate" type="datetime"/>

    We get the datatype through the IDocumentSummaryField-interface getType() function.


    Wednesday, October 1, 2014 8:38 AM
  • Could you get a fixml of a document that datatype is defined correctly, and the "string" one and compare the results of the specific field in question?
    Tuesday, October 7, 2014 7:37 PM
  • We identified the problem now:

    We have a main view "Webcluster" and after adding new fields to the index profile and doing a cold reset we found out that multiple collections were not added to the main Webcluster view. Thus the newly added fields were not recognized in the FAST API when checking for the datatype.

    After reorganizing the views we had to reinstall the qrserver. Things are working smoothly again now. Thanks for the help anyways, Patrick.

    Tuesday, October 14, 2014 1:27 PM
  • Thank you for the follow up and providing the  workaround/solution.
    Tuesday, October 14, 2014 4:05 PM