I looked again at what is available natively under Java for locale-specific
date formatting. The only game in town seems to be DateFormat, which has
only 9 canned configurations for date/time formatting. The one that most
closely matches what we do now comes out like this for US:
' 11/30/18
I'm sorry, you'll need to provide more details about what exactly you are
running into trouble with.
Specifically, this: " But the current crawler using the SQL queries which
is hard to query under a path. "
Karl
On Fri, Nov 30, 2018 at 4:42 AM Sivakoti, Nikhilesh <
Hi Team,
We have been migrating the indexes from GSA to Elastic search. We are using
Manifold crawler with alfresco webscript connector.
Crawler is able to crawl the less number of indexes. But it fails to crawl the
indexes in QA environment.
We have more than 80 million+ transactions in QA
Hi Mario,
I am glad your job is running now.
The manual section you describe gives you the number of postgresql handles
you need. That computation is correct. But the number of worker threads
is what is at issue.
Just because your system has tons of processors available doesn't mean you
can
The dates/times for this page are formatted as follows:
org.apache.manifoldcf.ui.util.Formatter.formatTime(clientTimezone,
pageContext.getRequest().getLocale(), js.getStartTime());
But the code for formatTime pays no attention to the preferred format for
the locale:
public static String
Hello Karl,
Can I change the datetime format < MM-dd- hh:mm:sss > to have < -MM-dd
hh:mm:ss > or < dd-MM- hh:mm:ss > ?
Thanks,
